public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: CPU issues with Speakup
Date: Sat, 30 May 2009 14:12:50 +0800	[thread overview]
Message-ID: <2A1B7544039B4FB1BFA6C299EBBC61C9@bouncy> (raw)
In-Reply-To: <alpine.DEB.2.00.0905291130080.24326@speech.braille.uwo.ca>

I know for a fact espekupd wakes up the processer 100 times a second 
according to powertop.
Use of usleep perhaps? Haven't looked at the code.
raises wakeup rate on my eeepc from 12.3 a second to 112.3 once espeakupd 
starts.
Regards, Kerry.

----- Original Message ----- 
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 29, 2009 11:32 PM
Subject: Re: CPU issues with Speakup


On Fri, 29 May 2009, Hermann wrote:

> On my notebook I've only tested the latest GRML 2009-05-RC1 in live mode.
> Although the CPU load is quite normal, e.g. about 6.0%sy, I observe about
> 12500 wakeups per second, which seems extremely high.
> Hardware: Intel processor of 2,7 Ghz and 512 MB RAM.

That does seem pretty excessive.  Where are you getting that wakeup
rate from?  I don't think our scheduling should be bringing anywhere
near that figure.
   Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


  parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hermann
 ` Kirk Reiser
   ` Hermann
     ` Samuel Thibault
       ` Hermann
         ` Chris Brannon
           ` William Hubbs
   ` Kerry Hoath [this message]
     ` Kirk Reiser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2A1B7544039B4FB1BFA6C299EBBC61C9@bouncy \
    --to=kerry@gotss.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).