RE: [misterhouse-users] Performance Issues - Slowing to a halt -NewInfo

[Neil W. <ne...@nw...>]

Lee,

>What is using the CPU cycles? Is it definitely MH?
Absolutely, definitely the main MH app (Not the MH_Proxy)
Once MH has gone thought the roof. I can kill the DCAM and the MH app still
stays at 99%.
Once I have restarted the main MH app (leaving the MH_Proxy still running)
CPU usage is back to normal.

>Are you looking in the TaskManager/Processes?
Most definitely.

Neil.

-----Original Message-----
From: MH [mailto:mh...@va...]
Sent: Wednesday, 20 October 2004 2:57 AM
To: mis...@li...
Subject: RE: [misterhouse-users] Performance Issues - Slowing to a halt
-NewInfo


What is using the CPU cycles? Is it definitely MH?

Are you looking in the TaskManager/Processes?

Lee

-----Original Message-----
From: Neil Wrightson [mailto:nw...@ho...]
Sent: 19 October 2004 13:15
To: mis...@li...
Subject: Re: [misterhouse-users] Performance Issues - Slowing to a halt
- NewInfo


Hi All,

Thanks for the help so far. Answers to questions are

1) What happens when you only run the dcam server? Works fine, no memory or
cpu hogging. stays constant.

2) Running windows 2000 pro, 1.5GHz, 256MB ram (was 128MB)

3) Tried running standard MH, ie ini and code_dir. Did not make any
difference.

4) Memory usage always stays the same for all apps
    MH_Proxy = 23MB
    MH          = 45MB
    DCAM      = 12MB

It is always the main MH that starts to gradually use up cpu power, but only
if started after DCAM.

If I start MH_Proxy then MH and THEN DCAM in this order the CPU usage stays
between 4 & 20% and the MH loops per second is around 22.

If MH_Proxy and MH are running then the loops/sec is 10..11. If I now start
DCAM it jumps to 22. Everything still works fine, but only if I specifically
start DCAM last???


At 04:39 AM 10/18/2004, Neil Wrightson wrote:
>Hi All,
>
>Bit more info. I have upgraded to 256MB memory and it still dies.
>But, I have some more info.
>
>Scenario 1
>1st Start Local MH X10 Proxy
>2nd Start Local MH.
>This is how I have been running reliably for the last 3 months 24/7
>Results
>Scan rate       - Average of 10 loops per second.
>CPU Usage       - 2%       (Constant)
>Mem Usage       - 174KB (Constant)
>
>Scenario 2
>1st Start DCAM Server
>2nd Start Local MH X10 Proxy
>3rd Start Local MH.
>Results
>Scan rate       - Starts at 22 loops per second.
>Decreases over 15min period to 1 per second
>CPU Usage       - Starts at 10% , Climbs to 100% over 15min period
>Mem Usage       - 174KB (Constant)
>
>If MH Only (not Proxy) is restarted then Scan rate goes back to 22/Sec and
>then slowly decreases.
>CPU usage drops back to 10% and then starts to climb again back to 100%
>
>Starting the DCAM app after MH proxy and MH are already running causes the
>scan rate to jump up to 22 times per sec, CPU usage fluctuates between 4%
>and 20% but does not increase to 100% as per above results.
>
>Question 1
>What is the interaction between MH and DCAM that causes the abnormally high
>scan rate.
>
>Question 2
>Why does MH use so much processing power when DCAM is running. Eventually
>strangling itself.
>
>I would have thought that there should be no interaction between these two
>apps.
>
>Thanks,
>
>Neil.
>

---
Outgoing mail is AVG certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 15/10/2004



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
________________________________________________________
To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365