[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zaurus-chatter
Subject:    [Zaurus-chatter] OZ users, help me get you a 50% speed increase!
From:       Joe Chott <verxion () yahoo ! com>
Date:       2002-08-26 16:31:09
[Download RAW message or body]

Hello everyone.

There are (from what I can tell), many people that are suffering
from this problem, some without realizing it.  From what I can
tell, if we can get this fixed, those of us running OZ could see
greater than a 50% increase in speed after a suspend.

Harlekin on the Opie team has asked for some information to help
track down the bug, and who/how many people have it.

Here is how you can identify the problem:

1. Only do this if you are running OZ (OpenZaurus) on your
Zaurus, and not the Sharp ROM.
2. Restart Opie from the Settings->Shutdown program
3. Run System Info from Settings->System Info
4. Go to the CPU tab
5. Look at the red load line.  It should be quite low, nearly
0%.  This represents your Application CPU usage.
6. Look at the green load line.  It is probably quite high -
nearly 100%.  This represents your System CPU usage (and is
really just the idle task consuming available cpu cycles)

So far, everything is as you would expect.  Now try this:

1. Suspend your Zaurus.
2. Resume your Zaurus.
3. Look at Sytem Info.
4. You should see a very rapid inversion of the red and green
lines.
5. Once things steady, you will see the red load line at roughly
80 - 95%.  It turns out this is because qpe is for some reason
using all available cpu resources.
6. Once things steady, you will see the green load line anywhere
from 0% to 20% cpu usage.

qpe is taking your valuable cpu time after a resume!  This slows
everything down.  You will notice if you compare, that things
launch and run noticably faster directly after a reboot or
restart of opie than they do after a resume from suspend.

If you found your application load (the red line) at above 5%
after the second test above, PLEASE email opie@handhelds.org
with the following information so we can get this bug fixed:

1. What version of opie are you running (shows in system info)
2. Which version of OZ (Open Zaurus)
3. Do you have any peripherals installed in CF or SD?  If so,
please list them.

Sorry to bug you all, but we are being denied a ton of cpu
cycles I think we could put to much better use!  :)

-Joe Chott

> At Samstag, 24. August 2002 17:03 Joe Chott wrote:
> > Ok, I am new to the Z, and new to OZ, so I may have
> something
> > configured wrong, but here is what I am noticing:
> >
> > I reboot my Z, and then load system info.
> >
> > I see 0% system cpu usage and 0% application cpu usage.
> >
> > Then I suspend, wait 1 minute, resume.
> >
> > Now I see things in transition, and when it stabilizes, I
> end up
> > seeing 20% system cpu usage, and 80% application cpu usage.
> >
> > Repeating another suspend/wait 1 minute/resume cycle/wait
> for
> > cpu usage to stabilize, and it ends up the same as just
> previous
> > - 20% system cpu usage, 80% application cpu usage.
> >
> > If I now reboot, and then run system info, the process
> repeats
> > yet again.
> >
> > I have seen many email postings and irc reports from people
> > saying that their application cpu usage ends up being 80% in
> OZ
> > and to restore it to "normal", they have to reboot, so at
> least
> > in that, I am just like everyone else.
> >
> > What I would like to know is, is there anything we can do
> about
> > this?
> >
> > -Joe Chott

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Zaurus-chatter mailing list
Zaurus-chatter@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zaurus-chatter
[prev in list] [next in list] [prev in thread] [next in thread]