I'm using the 3.0pre2 Unix VM under Linux 2.4.0, with a 3.1 image. What I'm finding is that:
* normally things run pretty well; if I do a Message Tally I see about 80% of the time being spent in Delay>>wait. The CPU usage is below 5% for Squeak.
* sometimes, though, Squeak uses about 100% of a CPU, and if I do a similar Message Tally, I see 75% of the time being spent in EventSensor>>nextEventFromQueue.
It can go from the "good" state to the "bad" state just by being left alone with no interaction.
Saving the image, quitting, and restarting fixes this problem.
Any suggestions?
To clarify, does it *stay* in the bad state, once it gets there?
-Lex
Ned Konz ned@bike-nomad.com wrote:
I'm using the 3.0pre2 Unix VM under Linux 2.4.0, with a 3.1 image. What I'm finding is that:
- normally things run pretty well; if I do a Message Tally I see about 80%
of the time being spent in Delay>>wait. The CPU usage is below 5% for Squeak.
- sometimes, though, Squeak uses about 100% of a CPU, and if I do a similar
Message Tally, I see 75% of the time being spent in EventSensor>>nextEventFromQueue.
It can go from the "good" state to the "bad" state just by being left alone with no interaction.
Saving the image, quitting, and restarting fixes this problem.
Any suggestions?
Ned Konz currently: Stanwood, WA email: ned@bike-nomad.com homepage: http://bike-nomad.com
On Friday 23 February 2001 08:51, Lex Spoon wrote:
To clarify, does it *stay* in the bad state, once it gets there?
Good question. I get so annoyed working with an image in this condition that I tend to save it and restart it. I assume that (since I'd already left it sitting and came back to it when it was in that state) that it had been like that all along once it had gotten into that condition. But I could have just walked up to it and tried to interact with it at the beginning of a 5-minute long bad spell that would have gone away on its own; I don't know.
I've been leaving my 3.1 image up since then overnight to see if it comes back; it hasn't so far. I'll keep my eyes open, though.
On Tuesday 20 February 2001 21:15, Ned Konz wrote:
I'm using the 3.0pre2 Unix VM under Linux 2.4.0, with a 3.1 image. What I'm finding is that:
- normally things run pretty well; if I do a Message Tally I see about
80% of the time being spent in Delay>>wait. The CPU usage is below 5% for Squeak.
- sometimes, though, Squeak uses about 100% of a CPU, and if I do a
similar Message Tally, I see 75% of the time being spent in EventSensor>>nextEventFromQueue.
It can go from the "good" state to the "bad" state just by being left alone with no interaction.
Saving the image, quitting, and restarting fixes this problem.
Any suggestions?
OK, more details: I did about 10 seconds of MessageTally without moving the mouse.
Here's when it gets slow (system CPU at 95% for Squeak process): - 558 tallies, 9715 msec.
**Tree** 99.8% {9696ms} DisplayScreen>>doOneCycleMorphic 99.8% {9696ms} PasteUpMorph>>doOneCycle 99.8% {9696ms} WorldState>>doOneCycleFor: 95.0% {9229ms} WorldState>>doOneCycleNowFor: |89.4% {8685ms} HandMorph>>processEvents | |89.2% {8666ms} EventSensor>>nextEvent | | 89.2% {8666ms} EventSensor>>nextEventSynthesized | | 46.8% {4547ms} EventSensor>>primKbdNext | | 42.5% {4129ms} EventSensor>>primMousePt |5.6% {544ms} PasteUpMorph>>runStepMethods | 5.6% {544ms} WorldState>>runStepMethodsIn: | 5.6% {544ms} WorldState>>runLocalStepMethodsIn: | 2.7% {262ms} StepMessage(MorphicAlarm)>>value: | 2.7% {262ms} NCLineEndConstraintMorph(Morph)>>stepAt: 4.8% {466ms} WorldState>>interCyclePause: 4.8% {466ms} Delay>>wait **Leaves** 46.8% {4547ms} EventSensor>>primKbdNext 42.5% {4129ms} EventSensor>>primMousePt 4.8% {466ms} Delay>>wait Then I save and quit, and restart. Then it looks like (system CPU at <2% typically for Squeak process):
- 638 tallies, 13107 msec.
**Tree** 99.8% {13081ms} DisplayScreen>>doOneCycleMorphic 99.8% {13081ms} PasteUpMorph>>doOneCycle 99.8% {13081ms} WorldState>>doOneCycleFor: 97.2% {12740ms} WorldState>>interCyclePause: 97.2% {12740ms} Delay>>wait 97.0% {12714ms} primitives **Leaves** 97.0% {12714ms} Delay>>wait
Why would this happen? Anything to look for?
squeak-dev@lists.squeakfoundation.org