New issue
Advanced search Search tips

Issue 774656 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Optimize size of PeriodicWave tables

Project Member Reported by rtoy@chromium.org, Oct 13 2017

Issue description

Experiments have shown that for the basic oscillator types, using 4096 coefficients produces exactly the same results as using 2048.

The spec, however, says we need to support 8192.  That's a pretty big increase in size.

As an optimization, it might be possible to adjust the table sizes of the PeriodicWave. For all PeriodicWave sizes, set the minimum size to be 2048.  When creating a PeriodicWave, find the index of the last non-zero value and set the wave size to the next power of two.

For the basic oscillator sizes, we can, perhaps, just use 2048 instead of the 4096 coefficients we used today. This would make the table half as large, which would be a big help on Android.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Oct 15

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment