Print

[Fan of Zappa]

  Any idea why relayer would use 70% cpu resources? I am running Win 8.1, iHouse, PCC.

Bob

[Tuicemen]

I must admit I haven't run X10Relayer on 8 or 8.1
which version of X10relayer are you running?
I know there are extra steps that need for running servers from 7 and 8 and this might be causing the issue.
Since I only have 8.1 on a laptop I'll have to fire it up and do some testing.
I also found X10relayer like to be on a system without clients and this might be what is causing a CPU usage spike.
As will having it allow connects from outside your home network (the internet).

[Fan of Zappa]

V 1.0.2.0. It will not close either. I used taskman to close it. Restarted it using PCC>plugins>run. works great when I do it that way. The problem persists each time I start PCC. If I stop relayer using taskman and restart using PCC>plugins>run it works fine again. 

[Tuicemen]

ok I'll load it and see what I can come up with

[Tuicemen]

Ok PCC may be holding on to it.
I may have to change how PCC starts it.
If you start X10relayer first then PCC does it work OK  or only if you close and start from the Plugin run button?

[Fan of Zappa]

I came home today after leaving it on all day long to find PCC using 47% and Relayer using 48% for a total of 95% CPU usage. I closed both programs and just loaded Relayer per your request. So far 0.3%. I will keep it running all night and day and report back to you tomorrow. I am using a laptop that only runs my HA stuff.

[Fan of Zappa]

Today I came home and Relayer was at 0%. I will close relayer, open PCC (closing relayer, as it will start automatically) and let you know what I find tomorrow.

[Fan of Zappa]

Tuice, Sorry for the missed day. Today I came home PCC was at 37% (running for two days). I will close it and start the test again with both running. Have you been able to duplicate any of this?
Bob

[Tuicemen]

Not as yet but I have made some changes to the intervals PCC contacts X10Relayer.
I'm just wondering what all is talking to X10relayer at your place?
I may have to fire up more devices  to see if that does anything.
I know Kenrad had seen a spike in CPU and Mem usage but he had a very Large setup with I believe 6 TAC devices too in the mix. Moving to a older version of relayer solved the issue for him.
Can you email me your PCC mysettings.xml file that way I can get a closer duplication of your setup here.
That may help weed this out. Also in X10relayer click to clear the log then check the log network activity and restart X10relayer after at least 2 hours copy the log file and send it to me as well.

[Tuicemen]

Since it appears the issue is the calls made to X10relayer I've scaled back the frequency PCC pings X10relayer.
The pings keep X10relayer from disconnecting a inactive client, however I discovered PCC was doing this even though it wasn't required this may be the same for BlueWatch.
Add in TAC, BlueWatch and a few more PCC clients and it is not hard to see why x10relayer can use so much memory.
Once I get your settings file and log file I'll see if the new changes help or will shed any light on another area for change.

[Tuicemen]

I Guess I should have asked for the X10relayer setting file too
It looks like you have both loading the X10drivers so both are attempting to send and process receives
if this is the case that's the reason for the high memory usage.

[Tuicemen]

Ok I can confirm x10relayer if configured to handle the x10 drivers and Have PCC running as well handeling them your memory use will spike to the point of locking up and only using the task manager will you be able to close it. In my case I also needed to use the task manager to close PCC.
I've added code to PCC to catch this and throw a critical message at start up.
I'll also look at adding something to X10relayer for this.
I'll mark this as resolved.
 

[Fan of Zappa]

Tuice, The new version took care of it. Thanks!  .