8Sep Fri2006 | London Automated Testing Conference
We had a liquid dinner at the pub last night: guinness, on the
tab of all those people who pay for adwords advertising. My
hangover is slowly engaging.
Really good talk about performance testing at google, with
JMeter the tool of choice. During dev they run nightly performance
tests with a shiny graph for dev/management every morning. This
lets you catch any change that kills performance within 24h of the
check in.
Good quotes. "Performance testing should not find memory leaks,
but it can". And on power point presentations from vendors on
products, 'I consider them guilty of wasting five hours of my
life'. And as for performance data collection, "even at google you
could run out of disk space"
One interesting point: 72h is consider a good time for a
longevity test. Maybe rebooting machines/apps every night is just
the simplest solution. I'm sure we have a ScheduledReboot {}
component somewhere, and if not, I could do it fairly trivially,
race-conditions notwithstanding.
|