Many Conditions running : CPU increased !

nslmanu · #1 September 11th, 2009, 04:53 AM

Hello,

After many weeks of utilization, i have now many events following many conditions.

The problem is that the CPU runs higher now than few weeks ago ...

If i look the logs i saw that the "checking conditions function" runs all time ...

I don't know if i have done the right things, but is there something to do to use correctly many events with conditions ?

Put diferent times on "Cannot re trigger for XXX seconds" for each events. It is the correct way ? I don't know.

Thanks in advance if somebody as any help ...

Here is what i have put :

kaldoon · #2 September 11th, 2009, 06:28 AM

Whow high is your CPU utilization? How many events are running? Can you attach a event log to see? What version of HS are you running?

nslmanu · #3 September 11th, 2009, 06:40 AM

Actually i have 17 "Condition" events. I use the version 2.3.0.19.

In fact actually it runs at less than 10 % CPU because i put "CANNOT RETRIGGER FOR xxx SECONDS" for EACH conditions events.

If a remember, it was nearly 1 per second ... at a point that my interface HS2 on the server ( where we can saw the logs in real time ) freezes.

Now it's fine, but with setting condition with few seconds or X dozen seconds.

kaldoon · #4 September 11th, 2009, 07:09 AM

Let's take a look at a couple of your conditions/events to see what they look like.

nslmanu · #5 September 11th, 2009, 08:50 AM

here is ...

nightwalker · #6 September 11th, 2009, 11:02 AM

I hope this makes sense to you but you could make those examples a lot more efficient if you changed them around a little bit.

for example #1
It looks to me like that command will trigger every minute (depending on what the "do not trigger" setting is set to as far a seconds.
Instead of a condition why not have it setup as a status change, then HS won't be looking at it until that status changes, instead of every 60 seconds or so.

for example #2
Almost the same. change it from condition to a status change on the Virtual Velux (whatever that is

), with a condition of the DS10 being off. This way HS will only be looking at the event when the status changes.

Example #3 I'm not sure about but it looks like it will trigger every 60 seconds, depending on the do not re-trigger setting. is that what you intend?

nslmanu · #7 September 12th, 2009, 08:58 AM

Quote:

Originally Posted by nightwalker

for example #2
Almost the same. change it from condition to a status change on the Virtual Velux (whatever that is

), with a condition of the DS10 being off. This way HS will only be looking at the event when the status changes.

It's a little bit strange, because if you want me to select the status change only ON the Velux, what i will do if the Second will change ? i'll need so to create a second trigger based on the DS10

It's really First OR Second, the condition depend of 2, both has the same for me ... But sure that i don't really know how HS2 works ... so maybe i'm wrong.

nightwalker · #8 September 12th, 2009, 09:57 AM

Quote:

Originally Posted by nslmanu

It's a little bit strange, because if you want me to select the status change only ON the Velux, what i will do if the Second will change ? i'll need so to create a second trigger based on the DS10

It's really First OR Second, the condition depend of 2, both has the same for me ... But sure that i don't really know how HS2 works ... so maybe i'm wrong.

I completely glazed over the OR in that event. sorry! What I'm trying to get to is that event is going to trigger every 60 sec or so, that's a lot of event triggering and if you have a lot of those types of events running it could conceivably slow things down a bit.

nslmanu · #9 September 12th, 2009, 10:53 AM

I guess i have no more solutions than putting : CANNOT TRIGGER and few seconds or dozen seconds.

nightwalker · #10 September 12th, 2009, 11:21 AM

The way you have it setup it's the only way to slow it down a bit. Anytime you trigger on something just being on, with no other condition, it's going to fire every 60 sec or so, unless you set the cannot re-trigger. In my own system I avoid those types of conditions and instead like to have at least two conditions that have to be met.

nslmanu · #11 September 12th, 2009, 01:10 PM

ha ok ... so how you use or how you do some conditions ? because on HS2, conditions are the base of this system, no ?

nightwalker · #12 September 12th, 2009, 02:45 PM

Exactly! HomeSeer can run a ton of conditions, but you do have to be careful about conditions that will be more or less true "ALL" the time. Otherwise depending on the system you will get a slowdown, depending on what else it's doing.

Why have conditions running every second of the day if there is any other way to do it.

Uncle Michael · #13 September 13th, 2009, 10:48 AM

Quote:

Originally Posted by nslmanu

It's a little bit strange, because if you want me to select the status change only ON the Velux, what i will do if the Second will change ? i'll need so to create a second trigger based on the DS10

It's really First OR Second, the condition depend of 2, both has the same for me ... But sure that i don't really know how HS2 works ... so maybe i'm wrong.

What is the event action? If it is an X10 command or something else that takes some time or extra resource, that might be part of the problem. Having two events with identical actions that trigger on each of the two status changes will do what you want - and run only when a status change occurs. I realize many people have a conceptual problem doing it that way, but I think HS will be 'happier' if you do.

nslmanu · #14 September 13th, 2009, 01:58 PM

I understand your opinion ...But , how to do a test like this in ONE event for example :

If
a = on AND b = on
then
set c = ON
elsif
a = off AND b = on
then
set c = OFF
fi

BE CAREFUL : don't want to set c=OFF is b=off

I hadn't found the solution, so i had created 2 events ....

but i agree with you that doing 2 opossite tests will increase the cpu resource ...

Thanks in advance ... i have HS2 since 3 or 4 months now .. just begin to use it !

Rupp · #15 September 13th, 2009, 02:24 PM

Quote:

Originally Posted by nslmanu

I hadn't found the solution, so i had created 2 events ....

but i agree with you that doing 2 opossite tests will increase the cpu resource ...

Thanks in advance ... i have HS2 since 3 or 4 months now .. just begin to use it !

Events are the foundation of HomeSeer. You should be able to run hundreds of well written events on the lowest end server and not have an issue. Therefore I wouldn't worry about adding 2 new events. Just so you know you can also script your logic just as you outlined with a few minor modifications using vbscript.

nslmanu · #16 September 13th, 2009, 02:31 PM

that's the problem ... i don't know scripting in VBscript ... only Unix shell ...

Wadenut · #17 September 13th, 2009, 03:40 PM

The VB version of exactly what you posted would be:

Sub Main
If hs.Ison("a") and hs.ison("b") then
hs.execx10("c","On")
elseif hs.isoff("a") and hs.ison("b") then
hs.execx10("c","Off")
endif
End Sub

Save this as whatever.txt

Naturally, substitute existing devices for a,b,c. Ie: "A1","B2","C3"

nslmanu · #18 September 14th, 2009, 04:47 AM

yes it works,

Just after this i have done my first little script : putting the HS2 uptime in a virtual device !!!

Even if i hate the black point before the Uptime datas, it's ok for me ( see the screenshot ) ...

I saw that doing a script is better than creating many many conditions events ...

So i'll continue but i haven't found the test for example : "IF data is between X Degrees and Y Degrees" or another : More than X Degrees ... only found : Is device is Equal at X ...