Page 1 of 1
High CPU usage Homeseer
Posted: Sun Jun 06, 2010 8:08 pm
by phoenixb
Hi,
I have sinds a short month that when HS is running for about 1 week that HS is getting for about 60 to 70% usage of my CPU.
I have not change anything that can be the problem, so my question what is the best way to resolve this problem?
Regards,
Re: High CPU usage Homeseer
Posted: Sun Jun 06, 2010 11:05 pm
by Alexander
DJ,
Have the same problem, but i do know the cause at my place: polling the zwave modules.
Re: High CPU usage Homeseer
Posted: Mon Jun 07, 2010 10:03 am
by Bjochems
Do you use the PHNetwork plugin?
Re: High CPU usage Homeseer
Posted: Mon Jun 07, 2010 12:42 pm
by Snelvuur
I've had also high cpu, this was also because of polling z-wave devices. If i poll all my devices the events just wont run correctly anymore (lights jump on after 5 seconds instead of almost instantly when motion is detected)
Re: High CPU usage Homeseer
Posted: Mon Jun 07, 2010 1:23 pm
by phoenixb
I have Z-wave but i'm polling every 60sec. at this moment so i think this can not be the problem.
But i have running PHNetwork so what can i do to solved it (ok disable the plugin

only that is not the sollution)
Re: High CPU usage Homeseer
Posted: Mon Jun 07, 2010 2:01 pm
by Snelvuur
btw, at the moment when it polls all the devices.. if you have a motion z-wave device for instance going through homeseer, it will be slow/annoying delays.. dont know if they will fix that though.
i also once had some debugging still turned on, which created something like 400gb of text data cant remember which one it was (but you can check your homeseer folder to look for big files)
Re: High CPU usage Homeseer
Posted: Mon Jun 07, 2010 5:07 pm
by Bjochems
djdive wrote:
But i have running PHNetwork so what can i do to solved it (ok disable the plugin

only that is not the sollution)
I don't have these problems with PHNetwork but I know some forum members do.
When you disable the plugin for some days and you see no high CPU usage anymore you can assume the plugin is causing the problem. Then you at least know that the plugin is the problem...