Closed Bug 1072675 Opened 10 years ago Closed 8 years ago

Neural network simulation runs slower on Firefox

Categories

(Core :: JavaScript: GC, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1242691

People

(Reporter: luke, Assigned: fitzgen)

References

()

Details

Running this sweet simulation
  http://nxxcxx.github.io/Neural-Network/
gets about 12fps on Firefox and 60fps on Chrome.  A quick profile with the builtin profiler shows most of the time in JS.  The app is built with three.js.
Instruments claims over half the time is under InterruptCheck doing a nursery GC, and pretty much all of that is under js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::mark(js::gc::StoreBuffer*, JSTracer*) and in particular under js::gc::MarkArraySlots(JSTracer*, unsigned long, js::HeapSlot*, char const*)

There's some js::jit::ArraySpliceDense in there too, which might be where all those nursery arrays are coming from.
Component: JavaScript Engine → JavaScript: GC
NI so it doesn't slip through the cracks :)
Flags: needinfo?(terrence)
At the moment I'm getting:

Content Encoding Error

The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.

    Please contact the website owners to inform them of this problem.
Worksforme as of a minute ago....  Do you still see the content encoding error?
Nick, it sounds like this may be the same perf cliff you are currently looking at.
Flags: needinfo?(nfitzgerald)
Will check in after bug 1242691 and verify that the fix resolves both instances of the cliff.
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
Depends on: 1242691
Flags: needinfo?(nfitzgerald)
Running at a smooth 60fps most of the time now that bug 1242691 landed, although I am still seeing infrequent dips down to 45fps. I think it is safe to close this bug as a dupe of bug 1242691 now.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(terrence)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.