Timer alignment in separate web processes should not all sync up to the same point.
authorbarraclough@apple.com <barraclough@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 1 Mar 2016 23:33:36 +0000 (23:33 +0000)
committerbarraclough@apple.com <barraclough@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 1 Mar 2016 23:33:36 +0000 (23:33 +0000)
commit4e3828b62fd1f7d5404663ad243fff4616f868e5
tree8131b56bbb3f6946978acab1187c85c758733f3c
parentcd2b85f74668c2e894dabd68fcf001f4ab86703d
Timer alignment in separate web processes should not all sync up to the same point.
https://bugs.webkit.org/show_bug.cgi?id=154878

Reviewed by Chris Dumez.

For any given WebContent process it is desirable that timers are synchronized to a single
alignment point, but if all WebContent processes align to the same point then there may
be a thundering herd of processes waking up.

* page/DOMTimer.cpp:
(WebCore::DOMTimer::alignedFireTime):
    - align to a randomized point.

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@197415 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/page/DOMTimer.cpp