Viktor Stanchev [:vikstrous] Reporter
	Description • 10 years ago

When I ran the gecko profiler on tcanvasmark I noticed that the test waits 2 seconds after each scene before moving on to the next one. My best guess is that this is done so that when it's run manually the score for each test can be visually observed. This is not necessary when the test is run on Talos, so if nobody has a good reason to keep this 2 second delay I recommend that we remove it (or at least shorten it to something reasonable).

Right now this delay is applied 8x times per cycle and there are 5 cycles per test, so the total wasted time by this is 8*5*2 = 80 seconds per test.

	Vishnu (:malayaleecoder) Assignee
	Comment 1 • 8 years ago

I guess this should solve the problem. It worked fine in my local machine :)

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 2 • 8 years ago

are the numbers the same before/after when you run it locally?  note, they are not going to be 100% identical, but very similar?

	Vishnu (:malayaleecoder) Assignee
	Comment 4 • 8 years ago

I am attaching the local.json files before and after my patch.
Joel, please have a look at it :)

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 5 • 8 years ago

these numbers don't look too different!

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 6 • 8 years ago

Comment on attachment 8771858 [details] [diff] [review]
Bug974620_v1.diff

Review of attachment 8771858 [details] [diff] [review]:
-----------------------------------------------------------------

please run on try with try: -b o -p linux64,win32,win64,macosx -u none -t all

	Vishnu (:malayaleecoder) Assignee
	Comment 7 • 8 years ago

https://treeherder.mozilla.org/#/jobs?repo=try&revision=8255f0bbb9ec

	Pulsebot
	Comment 8 • 8 years ago

Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d0cb076a4e73
tcanvasmark wastes time waiting after each scene. r=jmaher

	Carsten Book [:Tomcat]
	Comment 9 • 8 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/d0cb076a4e73