ActiveState Community Site - High CPU usage when idle - Comments

re: any news

ToddW — Tue, 17 Jun 2008 15:29:40 -0700

Hi Joseph,

There have been a number of changes made in Komodo's development tree to work this problem out. If this is proving to be a major distraction to your daily work, then I recommend either going back to the Komodo IDE 4.2.1 build or trying the Komodo 4.4.0b1 (beta) build, both found here:
http://downloads.activestate.com/Komodo/releases/

Cheers,
Todd

Any news?

JERichardson — Tue, 17 Jun 2008 13:57:15 -0700

I'm in the middle of an intense stretch of coding and this problem is driving me nuts. Any news on some kind of fix, workaround, anything?

Joseph

re: update

ToddW — Fri, 09 May 2008 18:36:49 -0700

I have found a few things that need some tweaking, which I'm working on adding to the Komodo 4.4.0a2 build (and then possibly back ported to the 4.3.3 build).

I'll post the details to the bug (http://bugs.activestate.com/show_bug.cgi?id=75961) when I've finished with the patches for it.

Cheers,
Todd

Nothing in 4.4a1

zacc — Tue, 06 May 2008 23:12:24 -0700

The latest 4.4a1 release has the same problems.

Any update?

JERichardson — Tue, 06 May 2008 18:20:19 -0700

Just wondering if you've been able to find out anything else about this problem. It's definitely still an issue for me; I would say it's more than an annoyance, but less than debilitating.

Joseph

Testing update

zacc — Thu, 17 Apr 2008 12:21:49 -0700

Ok, have disabled SVN and restarted the IDE. The CPU still thrashes, but only for about 10 seconds. Reactivated SVN and restarted - thrashing is down to 10 seconds as well, but playing with the IDE for 20 minutes, the thrash seems to get a little longer as the time that Komodo is being used passes.

I've also been playing with the "checking for off-line changes" to see what happens there.... and it picks up notepad initiated changes to the files fine and doesn't cause the CPU thrash.

Commiting files also seems to cause the thrash to occur - and causes the thrash time to increase significantly. In fact, checking a file in causes the CPU effort to become highly erratic - some 3 minutes after checking a file in Komodo is intermittently 20/40/30% cpu usage (never much below 5%)... it's obviously getting it's knickers in a twist about something. Some 10 minutes later and it's still flicking between "idle" and 7% usage every couple of seconds (with the occassional flick to 20%+).

Memory usage is also creeping up.

Re: still cpu problems

ToddW — Thu, 17 Apr 2008 12:16:27 -0700

Nod, thanks for confirming that. I've been comparing Komodo versions (4.2.1 to 4.3.2) and I notice that the SCC status checking on large projects (projects with lots of scc files), the Komodo 4.3.2 version is indeed a lot slower than the Komodo 4.2.1 version when updating the SCC status (during scrolling the project view, and periodic status checks).

I'll continue my investigations and will hopefully have some better explanations and/or fixes to this problem.

Cheers,
Todd

Update

JERichardson — Thu, 17 Apr 2008 12:14:17 -0700

I think I have to modify my "no difference" statement. I've been playing with it more and I would say that the problem still exists but the CPU usage accretes at a much slower rate. That is, instead of checking out 20 files, I have to check out 60 files to overwhelm the CPU. (The files are not necessarily checked out all at the same time.)

No difference

JERichardson — Thu, 17 Apr 2008 11:45:29 -0700

If the update has modified Komodo's behavior or improved the situation, I can not detect it. As I check files out and then in again, CPU usage creeps up and up.

Re: still not working (update)

ToddW — Thu, 17 Apr 2008 11:44:41 -0700

Comparing Komodo versions (4.2.1 to 4.3.2) I notice that the SCC status checking on large projects (projects with lots of scc files), the Komodo 4.3.2 version is indeed a lot slower than the Komodo 4.2.1 version when updating the SCC status (during scrolling the project view, and periodic status checks).

I'll continue my investigations and will hopefully have some better explanations and/or fixes to this problem.

Cheers,
Todd

Re: duplicate problem

ToddW — Thu, 17 Apr 2008 11:40:35 -0700

Hi Zacc, thanks for the input.

It is hard to tell whether this problem is stemming from the "scc status checking" or from the "perl syntax checking" (two separate components).

The scc status checking only fires on specific events like an "on-focus", "file-save", "periodic x mins check"), whilst the syntax checker always fires from document on-modify events. Also, it should not matter if you are connect to the network or not as the Komodo svn status checks are always offline except in the cause of an explicit "Refresh Status" command.

To find out which one is causing the problem, could you disable the subversion integration inside of Komodo and restart. Do you still have any CPU performance problems?

Thanks,
Todd

Duplicate problem ?

zacc — Thu, 17 Apr 2008 11:25:44 -0700

I've been experiencing high cpu usage on my machine running IDE 4.3.1, and have been watching this thread with interest waiting for 4.3.2 to arrive - which I quickly downloaded as soon as it became available. However, it doesn't appear to have fixed the problem - although the problem does appear to have morphed.

Firstly, my set-up - I'm using Komodo IDE to facilitate the development of a Perl based web-app, which compromises about 50 assorted .pl and .pm files. Running on Vista (spit) Home Premium dual-core laptop with 2GB ram on board, I typically have two or three different projects open, with approx 70-100 files across the projects and typically four or five files open for modification. I'm using SVN, with the repository running on a separate server.

What I'm seeing is this ..... when I'm constantly clacking away on the keyboard, CPU stays calm - but when I stop keying and allow the syntax checker to kick in (I've got the checker set to a 15 second delay atm) the CPU usage increase a little as the checker runs - but as soon as the checker finishes (and I get the green tick or, more often than not :-) the red exclamation mark) the CPU goes ballistic.

If the laptop is not connected to a network, the CPU runs 100% on one CPU for about 20 seconds. If I'm connected to the net (either 3G dialup internet or direct the network hosting the SVN server) - it stays high for about almost exactly 90 seconds (I've timed about two dozen runs so far).

To rule out a problem with SVN server, I've been using SmartSVN client on laptop to browser the repository during these hangs, and it flys - with no impact on the Komodo thrash timeout.

If, half way thru the 90 seconds cpu thrash, I type on the keyboard Komodo rechecks the code fine (albeit a little sluggishly) and the 90 seconds cpu thrash completes as expected at the 90 second mark from the original check finishing and not 90 seconds from time that the second check finished.

I've just checked the problem on another, more powerful (again dual core) machine and the trash periods are slightly less, but still consistent between like for like runs.

Re: still not working

ToddW — Thu, 17 Apr 2008 09:58:50 -0700

The CPU symptoms you are experiencing are still the same now? Or there was some improvement but it's still not the same as it was with Komodo 4.2?

I'll be doing some more testing on this today to hopefully discover any other issues relating to the scc performance.

Thanks,
Todd

4.3.2 does not fix the problem

JERichardson — Wed, 16 Apr 2008 13:38:59 -0700

As I said in the subject line....

This is really killing me. Is there something else we can do?

Yes

ToddW — Wed, 16 Apr 2008 13:19:40 -0700

The Komodo 4.3.2 has made a number of improvements to help address the SCC high CPU usage problems.

You should be able to use the Komodo "Help->Check for updates" menu to auto-update, or use the direct download link below:
http://downloads.activestate.com/Komodo/releases/latest/

Cheers,
Todd

High CPU usage when idle

JERichardson — Mon, 24 Mar 2008 14:17:08 -0700

Creating PHP source using Komodo 4.3 on Windows with Perforce.

When idle (I'm not typing, not browsing, just watching Task Manager), Komodo is using 30-40% CPU time. It doesn't seem to be that way when I first start Komodo. But after a short time it just bogs the machine, makes the fan comes on high. Any ideas?