- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Wed, 16 Jun 2010 08:49:50 +1200
- To: Chris Grigg <chris@chrisgrigg.org>
- Cc: public-xg-audio@w3.org
- Message-ID: <AANLkTil6p6YB-NoPAtLxABhADMnM_iZRCVzIcNGOWw4S@mail.gmail.com>
On Wed, Jun 16, 2010 at 8:22 AM, Chris Grigg <chris@chrisgrigg.org> wrote: > Further to my comment on the separate "Target platforms?" thread, on what > range of target platforms did you find the performance to be equivalent? > Are there any of our target platforms that are not capable of realtime > performance with that FFT implementation? I would worry about very skinny > clients not only for FFT but for any compute intensive operations. > Vlad's tests were on a desktop machine. We should do experiments on a mobile device and report back. However, I see no fundamental reason why the observed closeness in performance between JS and C would be unattainable in lower-end devices. Our ARM backend is less mature but that will improve. Asking another way: Are these accelerated JS implementation techniques you > reference deployed for all of our target platforms? > What are your target platforms, specifically? Anyway, we need to plan for the future, and it seems safe to assume that JS optimization techniques will spread to every platform where they're useful. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Tuesday, 15 June 2010 20:50:18 UTC