Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com
From: "Rajiv Patel" <scorn@pacbell.net>
Newsgroups: scea.yaroze.programming.codewarrior
Subject: Re: CodeWarrior eats cpu time
Date: 24 May 1997 05:15:14 GMT
Organization: SCEA Net Yaroze News
Lines: 26
Message-ID: <01bc67e8$95d689b0$010200c0@storm>
References: <01bc6733$b0926b30$010200c0@storm> <3385c429.1328259@news.scea.sony.com>
NNTP-Posting-Host: ppp-206-170-223-195.anhm01.pacbell.net
X-Newsreader: Microsoft Internet News 4.70.1161

Lee Stewart <lee@voxware.com> wrote in article
<3385c429.1328259@news.scea.sony.com>...
> On 23 May 1997 07:40:19 GMT, "Rajiv Patel" <scorn@pacbell.net> wrote:
> 
> >Has anyone noticed that CodeWarrior absolutely eats CPU time.  It
doesn't
> >matter which component - IDE, debugger or PSComUtil - they all nail the
CPU
> >meter to the ceiling.  This is in NT4.0, both before and after applying
> >Service Pack 3.
> 
> This is probably a quirk in the way they are handling Windows messages
> (or events for the Mac programmers out there).  If you sit in a tight
> loop getting these messages and and dispatching them you will see the
> CPU hit %100.
> 
> Is your system slower?  If your CPU was really %100 busy, you wouldn't
> be able to run other programs, etc.

Well, that's what I'd figured - I don't have any noticeable slowdown in
other apps, but it's a little annoying to see the CPU meter tag 100% all
the time - it means I don't know when something really *IS* eating the CPU.
 The CPU meter's been a godsend when crazy things happen like MSVC just
spinning during a compile eating CPU time and virtual memory for no good
reason...