On Fri, Nov 4, 2016 at 5:19 AM, vroad <[email protected]> wrote: > I've found another issue while working on Starling. TypedArray.set runs > significantly slower with short inputs. > Starling copies 80 bytes to copy the vertex data of each quad before doing > transformation, but this seems slow especially on Android. > A loop that copies 4bytes*20 elements runs significantly faster than set > function. I've experienced the same issue on .NET, so is this even possible > to fix? > > There is an issue on this as well, but not updated for a long time. > https://bugs.chromium.org/p/v8/issues/detail?id=3590
The implementation hasn't changed significantly since that bug was filed, it still calls into the runtime. That said, even if .set calls were lowered to inline machine code, I expect it's still going to be slower for small inputs because of the extra checks (checks like 'are the arrays of the same type', 'do they overlap in memory', etc.) -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
