On Thu, 26 Oct 2000 12:58:47 -0400 Kevin Fisher <kgf at golden.net> wrote:
>Ok, no problem...here's a better message tally...incidentally, whatever is 
>wrong with my image seems to be persisant now...when I start up Squeak it is 
>sluggish right off the start.  Doing an 'update code from server' (whether or 
>not there are updates available or not) will always cure it.

Kevin,

I'm guessing that this is related to your Delay problem and perhaps you already have it solved and emails are still crossing the great void, but here are some ideas in case the problem still persists:

The MessageTally (even the new one) looks quite normal. It is important to note, however, that MessageTally is basically watching one process and assuming that it is the only one doing anything of substance. It has no way of telling if the observed process is actually getting all the cpu time between observations or whether some other process is sneaking in and stealing all or most of it. It may be, therefore, that the other processes you mentioned in the Delay thread are, in fact, doing that. Evaluate the following two lines together.

Smalltalk garbageCollect.	"eliminate those about to be gc'd"
(Process allInstances collect: [ :each | {each. each priority}]) inspect.

This will show the processes that exist - there should be less than a dozen in a plain image. If you are seeing many more, they may be the culprits. If they are present in an image after saving and restarting, then they may be depending on some state information that did not survive (sockets, other OS resources, e.g.).

Another thought (and this may help others experincing similar sluggishness): try hitting cmd-period (or your platform's equivalent). If a process other than the UI process is hogging the cpu, you may be able to catch it in the act.

Cheers,
Bob