Hi Sascha,<br><br>we are outside of my technical abilities but I tried to translate what you said and put it on the wiki. If anyone would like to expand on this please do!<br><br><a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Hardware">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Hardware</a><br>
<br>Thanks<br><br><div class="gmail_quote">On Tue, Jun 9, 2009 at 2:52 PM, Sascha Silbe <span dir="ltr"><<a href="mailto:silbe@sugarlabs.org">silbe@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Jun 08, 2009 at 08:10:36AM -0400, Caroline Meeks wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can you give him instructions on how to gather data if he is going to be<br>
testing on school computers?<br>
</blockquote>
<br></div>
Measuring:<br>
----------<br>
<br>
Simple stuff (using a watch to determine time to certain events / "milestones", e.g. activities ring showing up) usually is all you want to do for more than a single or at most a few computers. With some work it should be automatable.<br>
<br>
For advanced usage I can (at least for now) only recommend to use "dstat -at --output dstat.log", always in combination with taking notes of when which events (activity started up etc.) happened (as dstat doesn't know about those and thus doesn't log them).<br>
If run in Terminal, you can use it to analyse activities.<br>
To analyse system startup you need to talk to Sebastian in order to find a way to let dstat run as early as possible.<br>
<br>
As analysing dstat output is quite some work I recommend to do this only as a second step and only for a few computers.<br>
<br>
<br>
Classification:<br>
---------------<br>
<br>
Performance usually is dependant mostly on the following factors. Using my desktop as an example for the output of the given commands:<br>
<br>
- processor ('cat /proc/cpuinfo')<br>
- generation / connection to mainboard (Socket AM2+)<br>
- can be looked up at Wikipedia<br>
- cache size ("cache size: 512 KB")<br>
- model ("model name: AMD Athlon(tm) X2 Dual Core Processor BE-2300")<br>
- frequency ("cpu MHz: 1000.000")<br>
- on modern and mobile CPUs, the value in /proc/cpuinfo ("cpu MHz")<br>
can be the _current_ value instead of the maximum<br>
- memory size and memory bus speed ('free' for size)<br>
- "Mem: 3544060" (total, is in kB)<br>
- on-board graphics might take up some of the memory (e.g. 512MB in my case -<br>
the system has 4GB)<br>
- hard disk speed ('hdparm -T /dev/hda /dev/sda')<br>
- "Timing buffered disk reads: 226 MB in 3.01 seconds = 75.02 MB/sec"<br>
<br>
<br>
<br>
HTH.<br>
<br>
CU Sascha<br><font color="#888888">
<br>
-- <br>
<a href="http://sascha.silbe.org/" target="_blank">http://sascha.silbe.org/</a><br>
<a href="http://www.infra-silbe.de/" target="_blank">http://www.infra-silbe.de/</a></font><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
iQEcBAEBAgAGBQJKLq94AAoJELpz82VMF3DayaYH+gI81PvDn5FKGkNgD7bRJMPt<br>
gDsuLl1EXDkP7YFWotv+LRGPPmILRZIl/4gliI6wqv1WkxyLOvkwmvfdsQHbjmTf<br>
51BNpOqVgFvhpp1DZuCH3cghxSrctXMOyhQlB6bD+O4odwafGmUUqAPkWCosryfw<br>
U8G0h0j8xJVG4GxZjMjYtvYzIAWERGW3GAiTrlwZYiScIF7VdMk3XjTCp0A1nfVW<br>
sfMgW8Lrg1ahK5fxWdPtYRiv4nmquMesYe+QE80L9M7r+RVW/ki4NSp9oH7csjPZ<br>
wRqQ7hKiuc1nn4xKPKdj2drxOE7SHpdiODZnMVbkLwoU1pcN0q6LLiqm2xf+hBs=<br>
=jWPY<br>
-----END PGP SIGNATURE-----<br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>