From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] LablGTK app maxes out CPU
Date: Wed, 05 Jul 2006 17:24:54 -0600 [thread overview]
Message-ID: <44AC4A46.3070105@gushee.net> (raw)
In-Reply-To: <20060704202117.GB15987@localhost>
Eric Cooper wrote:
>> That's how it was originally. But if you look again at my code, you
can see that the version with Unix.O_NONBLOCK is commented out. That's
because on one of my machines (the one with a newer version of GTK and
LablGTK, I believe), I got exceptions every time the program tried to
read the input.
>
> Right, me too. I use code like this to read from the channel inside
> the watcher:
>
> let try_read chan ~buf ~pos ~len =
> try Some (Glib.Io.read chan ~buf ~pos ~len)
> with Glib.GError "g_io_channel_read: G_IO_ERROR_AGAIN" -> None
Thanks for the tip. This does indeed eliminate the errors with a
non-blocking channel. But I still get excessive CPU usage. I have also
tried setting the priority on add_watch (both `DEFAULT_IDLE and `LOW).
Nothing seems to make any difference. It's true that my app does allow
other programs to grab a significant amount of CPU time when they need
it. But when my app is idle and not much else is running, 'top' shows it
using over 90% of the CPU. That's certainly not normal, and I would
think very undesirable.
A 'sleep' call might help, but the standard Unix.sleep only accepts
1-second increments, which is undesirable. But I can try a wrapper for
usleep() ... unless someone has a better idea.
--
Matt Gushee
: Bantam - lightweight file manager : matt.gushee.net/software/bantam/ :
: RASCL's A Simple Configuration Language : matt.gushee.net/rascl/ :
next prev parent reply other threads:[~2006-07-05 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 18:30 Matt Gushee
2006-07-04 18:59 ` [Caml-list] " Matt Gushee
2006-07-04 19:12 ` Eric Cooper
2006-07-04 20:00 ` Matt Gushee
2006-07-04 20:21 ` Eric Cooper
2006-07-05 23:24 ` Matt Gushee [this message]
[not found] ` <Pine.LNX.4.64.0607060354120.6166@home.oyster.ru>
2006-07-06 0:27 ` Matt Gushee
2006-07-06 2:46 ` Matt Gushee
2006-07-06 16:51 ` Jerome Vouillon
2006-07-06 19:16 ` Matt Gushee
2006-07-06 23:51 ` Matt Gushee
2006-07-07 1:26 ` SOLVED -- " Matt Gushee
2006-07-07 13:40 ` Jerome Vouillon
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=44AC4A46.3070105@gushee.net \
--to=matt@gushee.net \
--cc=caml-list@inria.fr \
/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