W3C home > Mailing lists > Public > public-respimg@w3.org > September 2013

Re: Compressive images test

From: Ben Callahan <ben@heysparkbox.com>
Date: Mon, 23 Sep 2013 11:04:14 -0400
Message-ID: <CADcYynS-Yh-1Tj_pS2DWq=kSsUWLmZP=N1QkL5XpsMtr-8=54Q@mail.gmail.com>
To: Andy Davies <dajdavies@gmail.com>
Cc: Jason Grigsby <jason@cloudfour.com>, "public-respimg@w3.org" <public-respimg@w3.org>
Andy, that would be great. I have a repo up here:
https://github.com/bencallahan/compressive-test with some tests for us to
play with. @pornel requested that we better compress the examples, so I
will be refactoring the imagesthemselves at some point. However, you could
use these tests to get your experiment setup.

Also, Id think we start with one of the more popular devices on the
market. Something like a Galaxy or an iPhone. Once we have the method for
testing established, we can publish how to test and open it up to anyone
with a device lab to test ALL THE DEVICES.

Let me know if I can help with something.

*Ben*

On Sun, Sep 22, 2013 at 3:18 PM, Andy Davies <dajdavies@gmail.com> wrote:

>
>> This led me to believe that instrumenting it was probably not going to
>> work because if we couldn't get good data from Chrome, the chances of
>> getting it from a feature phone is non-existent.
>>
>> I think we're looking at crude tests like what Ben suggested.
>> Progressively more challenging pages that we then have a bunch of people
>> test on a range of devices and ask people to observe behavior. Does it
>> crash the browser? Is scrolling slower? Etc.
>>
>> I can't think of a way to make it scientific, but perhaps we can do
>> something that is at least informative.
>>
>>
> Perhaps one way of doing this might be
>
> 1. Build two test pages - one with compressive images, one without
> 2. Find the crappiest device with a DPR of 1 and run Android 4.x and Chrome
> 3. Use Telemetry (http://www.chromium.org/developers/telemetry) to
> profile the pages loading on the device
>
> I'm quite happy to have a play with this to see if it gives us anything
> meaningful but can anyone suggest a suitable device?
>
> Andy
>
Received on Monday, 23 September 2013 15:04:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:40 UTC