Comments for happiest unalice ever

Comment on Standalone Talos V1.5 by Minnie tian

Minnie tian — Wed, 10 Jun 2009 02:11:20 +0000

I think it’s constant.Because I have countered this error from my first test to now .And I have checked the codes”GetPidsByName” and GetPrivateBytes”and “GetResidentSize” .Those functions both work.And there are results in tp_RSS.csv and tp_Privat Bytes.csv.But the results in byte seems too big .

Comment on Standalone Talos V1.5 by alice

alice — Sat, 06 Jun 2009 00:09:16 +0000

If it occasionally drops that error, it’s okay. If it’s constant (ie, hundreds of times) then there could be something wrong. Has something to do with occasionally being unable to access the associated information with the browser process, which seems to happen a few times in a normal Talos run.

Comment on Standalone Talos V1.5 by Minnie tian

Minnie tian — Fri, 05 Jun 2009 05:52:30 +0000

When I use it do a ff talos V1.5 test on Ubuntu 8.10,there always is a Error ,saying “Error in collecting counter: RSS and Error in collecting counter: PrivateBytes” .Is that a bug? please help ! Thanks!

Comment on Tshutdown Goes Live by John O’Duinn’s Soapbox » Talos now measures shutdown times

John O’Duinn’s Soapbox » Talos now measures shutdown times — Mon, 04 May 2009 19:39:23 +0000

[...] Basically, each Talos test assumed that the previous suite had already ended and exited browser successfully. However, sometimes (usually Vista!), we found that closing a healthy browser took longer then expected. This would cause the next Talos suite to fail out because of the lingering process left by the previous talos suite. This fix should greatly reduce intermittent oranges from Talos in mozilla-central, mozilla-1.9.1 and tracemonkey. In the few days since its been enabled, things look much better already! 2) Users care about shutdown times Just like we measure startup time, it feels right to measure shutdown time. It was never measured before, but once the idea came up, this felt like a good thing to measure. There are also some edge cases where users exit-and-quickly-restart firefox, which can become unhappy if the browser process is still slowly closing down. The curious can find more details in Alice’s blogpost here. [...]

Comment on Sheriffs Take Notice: We Can Retest Builds With Talos Sendchange by John O’Duinn’s Soapbox » Talos improvements

John O’Duinn’s Soapbox » Talos improvements — Fri, 24 Apr 2009 19:55:42 +0000

[...] case you missed this, its worth highlighting. The work catlee did in bug#468731 fixed 3 important recurring Talos [...]

Comment on Investigating Unthrottling Talos Boxes by Automated Talos Analysis | chris' random ramblings

Automated Talos Analysis | chris' random ramblings — Fri, 06 Feb 2009 03:45:17 +0000

[...] Although in these cases, the regression was actually a win in terms of performance, it shows that the algorithm works. The second regression is due to Alice unthrottling the Talos boxes. [...]

Comment on Talos on Mobile Performance Results Now Available by Mark Finkle’s Weblog » Talos for Mobile - The System Works!

Mark Finkle’s Weblog » Talos for Mobile - The System Works! — Sat, 31 Jan 2009 22:02:08 +0000

[...] for Maemo and Windows Mobile (not sure what’s up with mobile-wince-arm-dep-191). Recently, Talos was setup for the Maemo builds. We are collecting data for a few metrics. Tp3 (pageload time) is notably [...]

Comment on Investigating Unthrottling Talos Boxes by bernd

bernd — Sat, 10 Jan 2009 14:35:05 +0000

>Just for the record, this does break my heart just a little bit.

The tears will be over compensated by the love that you get from all the people waiting for the tinderbox to finally delivering its result. Just try to estimate how much hours you alone will save the project.

Comment on Auto-Rebooting Talos Boxen Saves The World by alice

alice — Wed, 07 Jan 2009 00:57:06 +0000

It’s unreasonable to attempt to track possible performance regressions based upon a side-effect of the initial Talos system set up. If we are interested in tracking how the browser behaves on a system that has been up for a long time, or re-using the same profile again and again, or some other long running metric then we should design a system to test it that is consistent and repeatable. As it was, we couldn’t say how long a machine had been up or how many browsers it had tested (and if any of those browsers were regressed and did something weird to the system, all the worse) - essentially it gave us no information about the sort of thing that you are interested in.

I think that we need a robust and varied approach to performance. We need to design different types of tests to cover different things that we are interested in. Attempted to fit everything under the Talos umbrella just isn’t the best route to that end.

Comment on Auto-Rebooting Talos Boxen Saves The World by Håkan

Håkan — Tue, 06 Jan 2009 08:10:07 +0000

Isn’t there a risk that there will be a class of performance bug that will now never show up on the radar? Can we be sure that e.g. the “auto rising” of memory after a period of continued use is not our problem?