W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: solving the CPU usage issue for non-visible pages

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 21 Oct 2009 16:43:54 +1300
Message-ID: <11e306600910202043wb4b1dd5mfeafe1552789ab1b@mail.gmail.com>
To: Brian Kardell <bkardell@gmail.com>
Cc: Maciej Stachowiak <mjs@apple.com>, "Ennals, Robert" <robert.ennals@intel.com>, Jonas Sicking <jonas@sicking.cc>, "public-webapps@w3.org" <public-webapps@w3.org>
On Wed, Oct 21, 2009 at 4:34 PM, Brian Kardell <bkardell@gmail.com> wrote:

> For example, I recently the Image Evolution demo from
> http://www.canvasdemos.com/2009/07/15/image-evolution/ as a kind of a
> performance test and let it run for three days - during which it was
> not "visible" 99.999% of the time.  Should processing stop - or just
> painting?  Painting wont happen because the OS says it wont right?
>

Depends on the OS, I guess. Performance testing is hard; for good
performance testing you need a carefully set up environment. It's OK to
require special browser configuration to make it believe that the user is
always present and the window is always visible. I don't think we need to
avoid Web platform or browser features because they might make performance
testing a bit harder.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Wednesday, 21 October 2009 03:44:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:34 GMT