#26 CPU Hogging
Hi...
I have Geoshell R8 running on Win2003 server. Now the
server has got a LOT of HUGE files and ppl open and
close documents all the time.
I also have LiteStep installed alongside Geoshell.
Now the bug happens in R7 as well.
Geoshell is pretty skinny when it comes to Memory but
for some reason the Geoshell does not share CPU
resources evenly.
Start-up....
Takes less than 20 secs....
After which Mouse and Keyboard freeze... HDD light is
off///
so i know it isn't due to VM,///
Then control returns... within 2 secs the same problem
repeats/// I can do 2 second shortcutting with Keyb and
mouse but its Very annoying when the same problem
doesn't happen if I am using LiteStep ///
Now I can increase the Priority of the Process then the
same problem happens every 6 secs...
So ... I am a bit lost on exactly why Geoshell needs to
hog the CPU so much ... as all its gotta maintain is
visible areas of its Bars ????? Does it handle Memory
as well ?????
Is it sharing, allocating, and managing resources on
the Computer??????
man_i@dodgeit.com
Logged In: YES
user_id=320753
This should have been brought up on the forums first ... I can't
duplicate this, and I don't have enough information about
settings and environment, or what's the user is doing to just
*guess* where a problem may lie.
The problem _may_ be in your settings, and I'd recommend you post
on the forums and see if there are others with similar problems
so we can narrow down the root cause before we place it as a bug
in the database.
Logged In: YES
user_id=320753
It's typical for Windows to report GEOSHELL as the process
using the CPU when it's actually applications launched BY
GeoShel, so it's hard to just accept this statement without
more information.
Are you experiencing this freeze-up only at start-up?
Does it go away after a few minutes?
Does it continue after all your startup programs have started?
Does it happen every time?
Logged In: YES
user_id=760994
This should have been brought up on the forums first ... I can't
duplicate this, and I don't have enough information about
settings and environment, or what's the user is doing to just
*guess* where a problem may lie.
The problem _may_ be in your settings, and I'd recommend you post
on the forums and see if there are others with similar problems
so we can narrow down the root cause before we place it as a bug
in the database.
Logged In: YES
user_id=760994
R4 Bugs item #1006555
GeoShell consuming CPU Resource....
hi about the "BUG"...
>>Comment By: Joel 'Jaykul' Bennett (jaykul)
>
>Date: 2004-08-10 18:37
>
>Message:
>Logged In: YES
>user_id=320753
>
>It's typical for Windows to report GEOSHELL as the process
>using the CPU when it's actually applications launched BY
>GeoShel, so it's hard to just accept this statement without
>more information.
>
Okay ... I understand that ... and I know that .. but the
bug is still there WHETHER there are applications already
running or none at all other than Geoshell.
Now the same thing does not occur with Litestep ... (so if
we have a
different shell the problem dissappears completely...)
Now the server is setup to use ActiveDirectory with around
200 User accounts ( 15 users at any given time with 30 MB
files on the server each)
Group Policy Objects deployed on the ActiveDirectory
configuring things like Internet Explorer, Software
Restrictions, Folder Redirection (Desktop, My Documents,
Start Menu , etc...) for about 15 machines.
The Server is also configured for DNS, WINS, Print Server,
Remote Administration, etc.
Now the Server Runs NTop ... Network traffic monitoring and
analysis utility.
So you can imagine that the number of Processes that run are
QUITE LARGE AMOUNT!!! That means this server is Resource
starved... (has very little , if none at all, CPU + Mem+
Device+ANYTHING access available)
Now WinExplorer shell takes about 10 - 20 MB when it runs...
LiteStep shell '' '' 2 - 12 MB
Geoshell '' '' '' 1 - 8 MB
When the server is up and running it consumes about 310 MB
of the 512 MB RAM available. has about 700MB of Virtual Memory.
On top of all these things... I use this as my workstation
machine... ( talk of Hardware abuse ... :-P )
Now you can see why I like to use Litestep/Geoshell....
But Geoshell used to work fine (old one still works fine)
before I deleted and replaced it with the new files.
I believe I used to use R4.9 or 4.10 ... Im just not sure...
I do not know the exact release number/....
Please post this to the forum as well for me please, if you
still can't duplicate the problem....
Thanking you.
Yours
Man_1
>
>Are you experiencing this freeze-up only at start-up?
>Does it go away after a few minutes?
>Does it continue after all your startup programs have started?
>Does it happen every time?
>
>----------------------------------------------------------------------
>
>Comment By: Joel 'Jaykul' Bennett (jaykul)
>Date: 2004-08-10 18:29
>
>Message:
>Logged In: YES
>user_id=320753
>
>This should have been brought up on the forums first ... I
can't
>duplicate this, and I don't have enough information about
>settings and environment, or what's the user is doing to just
>*guess* where a problem may lie.
>
>The problem _may_ be in your settings, and I'd recommend
you post
>on the forums and see if there are others with similar problems
>so we can narrow down the root cause before we place it as
a bug
>in the database.
>
>----------------------------------------------------------------------
>
>You can respond by visiting:
>https://sourceforge.net/tracker/?func=detail&atid=438277&aid=1006555&group_id=1204
>
Logged In: NO
Had the same problem in Windows 2000, it was one bf the
bars, in which I made a double click by mistake and the
whole system started to stop for about 30secs. then go again
for 5 secs.
Try deleting bars and make new ones, it helped me.
Logged In: YES
user_id=1437542
There are periods of time when GeoShell completely hogs the
CPU. I suspect this is b/c it runs in "AboveNormal"
priority by default. I fail to understand the reasoning
behind this. Why would you need to run a shell in higher
than normal priority? In most UNIX systems with bash
installed as the shell for a particular user, as soon as
that user logs in, bash runs under normal priority (not
realtime) and with no particular 'nice' value (as set with
libc's setpriority). IMHO, the shell doesn't need that many
clock cycles; it is primarily responsible for forking
processes and cleaning up terminated processes. Everytime I
reboot my computer, it takes me 20 seconds after I press
Ctrl-Shift-Esc to get to Task Manager, in order to change
the priority of GeoShell.exe from "AboveNormal" to "Normal";
this seems to fix all of the CPU hogging issues. Besides
this annoying aspect, GeoShell is still a superior
alternative to Windows Explorer ;-)
Logged In: YES
user_id=320753
You can actually just change the priority, it's a setting:
HKEY_CURRENT_USER\Software\geo\GeoShell\GeoShell Priority
3 = normal, 4 = below normal, etc.
Note of course that the lower priority the shell is, the
more likely it is to become non-responsive when another
application is hogging the CPU. Of course, the opposite is
also true: higher priority on GeoShell may allow geoshell to
hog the CPU, particularly if you have a misbehaving plugin,
or another process running under geoShell's priority setting
because of how it was launched...
That said, I think the problem this setting was designed to
address is not being fixed by the setting, so I'll make the
change in the next installer to have geoShell default to
"Normal" priority.