Hi, Just to be sure: Did you eliminate the most basic newbie mistake anyone can do in connection with high CPU usage? That is: Start your swiki image without the -headless switch, close all windows (especially transcripts etc.) in the swiki image and then save&close (with the swiki started).
HTH > On the system I'm working on, the system has already reached the > responsive state, and it continues to use the entire processor (has been > doing so for ~3 hours now). It is still relatively responsive. I'm > thinking that a poor hack of a fix will be to just renice the process to > about 2 or so if I can't figure something else out. > > Bill > > On Mon, 8 Apr 2002, Pierre Baillet wrote: > > > just as Stephan stated, I have the exactly same behaviour when starting > > the swiki. This startup time seems necessary for the smalltalk vm to > > start well and the swiki is almost unreachable during that time. Then > > the CPU usage drops and everything runs correctly... > > -=- Bill Denney -=- [EMAIL PROTECTED] -=- > Sum ergo cogito. >
