CPU Usage

(Getting a 'can't resolve newsgroup' error so I'm unable to post reply to 
the original thread)

Running Task Manager (Win XP) shows that sb4w.exe hovers around 80% to 90% 
CPU Usage (in the Processes page). I thought it might be different since 
it's 'nested' in wowexec.exe, but the Performance page shows CPU usage at 
100% and nothing else is running.

Is there a way to reduce Superbase's CPU usage? I was hoping to track down 
the reason for getting more frequent '"out of resources... subsystem 
error... restart your machine." (course I can't remember the exact error
msg 
even though I get it at least once a day).


"Peter Barus" <ViPr@Compuserve.com> wrote in message

news:1103_916546549@gatemo...
> On Fri, 15 Jan 1999 10:42:46 -0000, in sbv2.programming you
> wrote:
>> In NT workstation 4 the CPU usage is 100% when Superbase
> 2 is loaded.  Is it
>> possible to reduce this?
>
> I think not, but actually, it is not really using 100% of the CPU
> anyway.
>

Is this a current response to this extremely old message?

SB4W always did show 100% cpu usage, and somebody back in the early days
asserted that this was not really what was happening. I know of, and have heard
of, no way to change this (other than upgrading!)

If you are in XP, be sure to set up icons so that NTVDM is run in "separate
memory space". This helps a lot especially if you have more than one 16-bit
app running. NTVDM is often (frequently) (usually) left running after shutting
down any SB app (or other 16-bit apps), but I think I have noticed (no real
tests done) that it closes down if it is called up as a "separate memory
space" (really just an additional instance of the "NT Virtual Dos
Machine".

Whenever anything goes wrong with Superbase (or as is often the case, Windows),
you can effectively reboot the 16-bit subsystem by killing the NTVDM task in
Task Manager. I ALWAYS do this when developing new code, etc., or if anything
acts funny. I believe fragments of stuff are left in memory when NTVDM is there.
MS will not fix NTVDM anymore, since the last hotfix years ago.




On Thu, 17 May 2007 07:51:06 -0500, John Ciccone
<johnrc@NOSPAMsympatico.ca> wrote:

> (Getting a 'can't resolve newsgroup' error so I'm unable to post reply to
> the original thread)
>
> Running Task Manager (Win XP) shows that sb4w.exe hovers around 80% to 90%
> CPU Usage (in the Processes page). I thought it might be different since
> it's 'nested' in wowexec.exe, but the Performance page shows CPU usage at
> 100% and nothing else is running.
>
> Is there a way to reduce Superbase's CPU usage? I was hoping to track down
> the reason for getting more frequent '"out of resources... subsystem
> error... restart your machine." (course I can't remember the exact
error msg
> even though I get it at least once a day).
>
>
> "Peter Barus" <ViPr@Compuserve.com> wrote in message
>
> news:1103_916546549@gatemo...
>> On Fri, 15 Jan 1999 10:42:46 -0000, in sbv2.programming you
>> wrote:
>>> In NT workstation 4 the CPU usage is 100% when Superbase
>> 2 is loaded.  Is it
>>> possible to reduce this?
>>
>> I think not, but actually, it is not really using 100% of the CPU
>> anyway.
>>
>
>
>
>

John Ciccone wrote:
> (Getting a 'can't resolve newsgroup' error so I'm unable to post reply to 
> the original thread)
> 
> Running Task Manager (Win XP) shows that sb4w.exe hovers around 80% to 90%

> CPU Usage (in the Processes page). I thought it might be different since 
> it's 'nested' in wowexec.exe, but the Performance page shows CPU usage at 
> 100% and nothing else is running.

In XP?  I can believe that you ever see "sb4w.exe".  What you would
see 
is ntvdm.exe.  I am surprise that ntvdm would ever even get down to 80%, 
what exactly are you running that takes up the 20%. A second copy of 
SB3? Because even a second copy of SB

This has come up before.  I don't think SB2 or 3, is actually using the 
CPU in anyway that degrades other performance.  If anything needs 
resources, it will get them immediately.

And I really don't think that SB has any part in your out or resources 
error. I'd look at whatever accounts for the other 20% when ntvdm goes 
down to 80%.

Of course, I could be wrong.

JDK


> 
> Is there a way to reduce Superbase's CPU usage? I was hoping to track down

> the reason for getting more frequent '"out of resources... subsystem 
> error... restart your machine." (course I can't remember the exact
error msg 
> even though I get it at least once a day).
> 
> 
> "Peter Barus" <ViPr@Compuserve.com> wrote in message
> 
> news:1103_916546549@gatemo...
>> On Fri, 15 Jan 1999 10:42:46 -0000, in sbv2.programming you
>> wrote:
>>> In NT workstation 4 the CPU usage is 100% when Superbase
>> 2 is loaded.  Is it
>>> possible to reduce this?
>> I think not, but actually, it is not really using 100% of the CPU
>> anyway.
>>
> 
> 

Peter Barus wrote:

> 
> If you are in XP, be sure to set up icons so that NTVDM is run in
"separate memory space". 
>This helps a lot especially if you have more than one 16-bit app running. 
>NTVDM is often (frequently) (usually) left running after shutting down 
>any SB app (or other 16-bit apps), 

I have never seen this happen, ever.

>but I think I have noticed (no real tests done) 
 >that it closes down if it is called up
 >as a "separate memory space"
>(really just an additional instance of the "NT Virtual Dos
Machine".

Interestingly, when you open up a REQUEST that requires input, ntvdm 
will go down to 0 until you hit OK or Cancel!

In some ways, SB in ntvdm is just mimicking the behavior of System Idle 
Process when then is no 16 bit app running. If you look at System Idle 
under the process tab in will say 99% when nothing else is running. 
While TaskManager won't report CPU Usage in the Performance Tab at 100%, 
I think this is just because they have written the TaskManager to ignore 
System Idle Process in making the calculation.

On Thu, 17 May 2007 10:43:11 -0500, Peter Barus <peter@visualpricing.com>
wrote:

> I believe fragments of stuff are left in memory when NTVDM is there. MS
will not fix NTVDM anymore, since the last hotfix years ago.
>