W3C home > Mailing lists > Public > public-mwts@w3.org > May 2009

RE: Memory test blog post (was: My Action Item (ACTION-34))

From: Carmelo <carmelo@nist.gov>
Date: Tue, 12 May 2009 10:00:01 -0400
To: "'Dominique Hazael-Massieux'" <dom@w3.org>
Cc: <public-mwts@w3.org>
Message-ID: <003301c9d309$f188ca90$d49a5fb0$@gov>
Dom:

Thanks for the feedback.  Will work on it now.

Carmelo

-----Original Message-----
From: public-mwts-request@w3.org [mailto:public-mwts-request@w3.org] On Behalf Of Dominique Hazael-Massieux
Sent: Tuesday, May 12, 2009 9:48 AM
To: Carmelo
Cc: public-mwts@w3.org
Subject: Memory test blog post (was: My Action Item (ACTION-34))

Hi Carmelo,

Thanks for your draft. Some modifications proposed below.

Dom

Le jeudi 07 mai 2009 à 13:45 -0400, Carmelo a écrit :
> --------------------------------------------------------------------------------------------
> 
> Memory test Write up

As a title, maybe rather "Memory test for mobile browsers"?

> 
> As a result of a lack of tests addressing memory limitations on Mobile
> devices, the Test Suite working developed a test to evaluate memory
> limitation issues.

I propose the following rewrite that puts this in a bit more context:
A few months ago, we looked at how well <a
href="http://www.w3.org/blog/MWITeam/2008/10/06/performance_tests_and_mobile_browsers">existing performance test suites worked on mobile browsers</a>: they generally worked poorly (if at all), and in many occasions, the limiting factor was the memory required to run these tests.

As a follow-up, we have developed a <a
href="http://qa-dev.w3.org/2009/memory-test/json.cgi">simple test</a>
that allows to determine the maximum amount of memory a browser can
dispose of.

>   The test uses the JavaScript Jason's and the device ability to
> handle JSON textual data.

(I would drop this - handling JSON is really equivalent to handling
Javascript)

>    The test is interactive and  with every successful  pass of the
> test, it prompts the user to increase the number of JSON's

replcae "number of JSON's" by "size of data put in memory".

>  until an upper limit of 135,000 JSON's is reached.

"until an upper limit of 100 MB."

>   The user also has the ability to decrease the number of JSON's.

rather "If the browser fails to fetch a given amount of data, the user
can pick a lower target."

>   The test has two arguments, namely
> 
>       * l - length of test 
>       * d - difference (if omitted, half of length), used in the
>         "binary" search 

I would drop that... 

> The test can be executed by following this execution link.  The test
> source code can be found at the source link.
> 
> The Mobile Test working groups welcome your comments.   Any comments
> and/or suggestions can be sent to the  MWTS mailing list.
Received on Tuesday, 12 May 2009 14:00:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:08:03 UTC