Try restarting Squeak (not just Swiki). This occassionally happens at GaTech (after about a month of uptime). Restarting the Squeak process should do it.
BTW, be sure not to use the "save & exit" button as that will most likely keep the crazy processes around. If you can't solve it that way, try downloading a new Squeak image and replacing the old one (make sure that it's the same version of Swiki). That should work. Size of the Swiki should have nothing to do with it. We have servers that have 10,000 pages or so on them. Peace and Luck! Je77 On Wed, Nov 20, 2002 at 12:42:49AM -0800, Mike O'Brien wrote: > My ComSwiki has suddenly started using a lot of CPU time, where > it didn't before. The odd thing is that the code hasn't changed in > months. It's just been ticking along, running the Swiki. Now > it's eating CPU at a near-realtime rate (1 CPU second per second > of real time - nearly a spin loop). The Swiki still responds, though. > Stopping and restarting it has no effect. > > Luckily it's running on a four-processor server, so there's > no great heartburn, but I'd still like to know what's what. People > have steadily been adding pages but it's not a large Swiki by any > means. It has two or three dozen pages, tops. > > Could it be that the number of pages has grown to the point > where the garbage collector is thrashing? I know other people have > seen this, but in those cases it seemed to be platform-dependent. > This is a case where neither the platform nor the code has changed, > but the behavior has. > > Mike O'Brien
