Olli Pettay [:smaug][bugs@pettay.fi] Reporter
	Description • 10 years ago

The current value is 10ms which is too much for animations. frames get dropped rather easily.
Could we try 5ms?

But locally when I set the value to 5ms, I still see something like 
Slice: 21, Pause: 10.1 (When: 599.4ms, Reason: REFRESH_FRAME)
maybe that is just one slice taking too long.
I was testing using javascript.options.mem.gc_incremental_slice_ms

	Jon Coppeard (:jonco) (PTO until 14th September)
	Comment 1 • 10 years ago

We're currently looking at this, but 5ms is very ambitious - see bug 1057530 comment 7.

	Olli Pettay [:smaug][bugs@pettay.fi] Reporter
	Comment 2 • 10 years ago

This is not about the max pause. This about the REFRESH_FRAME slices.

	Olli Pettay [:smaug][bugs@pettay.fi] Reporter
	Comment 3 • 10 years ago

In other words, max pause is one issue, the average slice time a different one.
In CC we've now got average slice time to pretty low, but the first one (TraverseRoots effectively) and second to last (Unlink) slices take occasionally too much time.