Swap to SD cards: performance and burnout test

[Tomeu Vizoso]

On Tue, Dec 8, 2009 at 15:05, Emiliano Pastorino
<epastorino at plan.ceibal.edu.uy> wrote:
> Thanks for all your replies.
> I'll show you the results when we're done.
>
>> What's most important to the user is probably going to be the latency
>> (pointer "sluggishness", UI reaction time), though, and I don't have an
>> idea how to test that (still keeping in mind that it needs to be
>> comparable and repeatable).
>
> Agree.
> So long, we've seen that you can be running 15 activities (and more, but
> that won't make much sense) simultaneously and UI reaction time "seems" to
> be the same, while an XO with no swapping always crashes with 4 or 5
> activities running at the same time.

Btw, have you considered using compcache? It may have tradeoffs
interesting to you. Martin Dengler (added to CC) has run it quite
intensively on the XO.

Regards,

Tomeu

> I'll speak to my boss and see if these subjective results are acceptable...
>
> btw, right now I'm using a Verbatim SDHC 4GB C6 card, but I'll be trying
> more flavours
>
> On Tue, Dec 8, 2009 at 9:10 AM, Neil Graham <Lerc at screamingduck.com> wrote:
>>
>> On Tue, 2009-12-08 at 10:18 +0100, Sascha Silbe wrote:
>> > > I don't think it's terribly useful to test memory consuming
>> > > non-interactive tasks.
>> > The problem is that the only way to get _comparable_, _repeatable_
>> > numbers is to make the test non-interactive.
>> Yup, but that's looking where you didn't drop your contact lens because
>> the light is better over here.
>>
>> > What's most important to the user is probably going to be the latency
>> > (pointer "sluggishness", UI reaction time), though, and I don't have an
>> > idea how to test that (still keeping in mind that it needs to be
>> > comparable and repeatable).
>> Simply cannot be done, User interfaces are inherently based around,
>> well, interfacing with the user.  The user is a component of the system.
>> You could have a bot that does some automated clicking but you run the
>> risk of ignoring exactly the data that would be relevant.
>>
>> The behaviour of the user will change with he speed of the system,
>> sometimes that change will significantly change the speed of the system.
>>
>> An example is the user triggering an operation twice because the system
>> took too long to demonstrate it was responding to the first one.  Even
>> if the double action is handled gracefully, it makes extra work to
>> figure out what to do.
>>
>> When my daughter was younger she would just keep on clicking on supertux
>> until it appeared, bringing the system to a standstill while it launched
>> 20 copies.
>>
>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>
>
>
> --
> Ing. Emiliano Pastorino
> LATU - Plan Ceibal
> Av. Italia 6201 CP: 11500, Montevideo, Uruguay
> Tel: (598 2) 601 5773 int.: 213
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>



-- 
«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David
Farning