Announcement

Collapse
No announcement yet.

Lots of cpu being used

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Lots of cpu being used

    I tried to turn off plugins and this didn't help, so I turned on some debugging logging and I find this in the log, a lot...

    Could this be what is eating all the cpu? What is the trigger evaluation?

    Here it the details it says to post in here too

    Current Date/Time: 12/6/2017 11:31:54 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.368
    Linux version: Linux OpenHAB 3.4.79-sun7i #19 SMP PREEMPT Fri Oct 10 03:20:03 CST 2014 armv7l GNU/Linux System Uptime: 0 Days 6 Hours 8 Minutes 40 Seconds
    IP Address: 192.168.1.114
    Number of Devices: 386
    Number of Events: 63
    Available Threads: 199

    Enabled Plug-Ins
    2.0.38.0: BLLAN
    2.0.74.0: BLLock
    2.0.22.0: BLOccupied
    3.1.1.24385: Blue-Iris
    3.0.0.8: Chromecast
    3.0.6.0: Insteon
    3.0.0.28: Nest
    0.0.0.35: Pushover 3P
    3.0.6370.28796: UltraM1G3
    3.0.0.76: weatherXML
    3.0.1.130: Z-Wave

    ----

    ec-06 11:14:35 PM EVENT DEBUG 11:14:35:1277: Dequeue event trigger, queue size: 0 Priority queue size: TYPE_TIME
    Dec-06 11:14:35 PM EVENT DEBUG 11:14:35:1239: Queuing Trigger Evaluation: TYPE_TIME Queue size is: 0
    Dec-06 11:14:34 PM EVENT DEBUG 11:14:34:3156: Dequeue event trigger, queue size: 0 Priority queue size: TYPE_TIME
    Dec-06 11:14:34 PM EVENT DEBUG 11:14:34:3096: Queuing Trigger Evaluation: TYPE_TIME Queue size is: 0
    Dec-06 11:14:33 PM EVENT DEBUG 11:14:33:0968: Dequeue event trigger, queue size: 0 Priority queue size: TYPE_TIME
    Dec-06 11:14:33 PM EVENT DEBUG 11:14:33:0924: Queuing Trigger Evaluation: TYPE_TIME Queue size is: 0
    Dec-06 11:14:32 PM EVENT DEBUG 11:14:32:2895: Dequeue event trigger, queue size: 0 Priority queue size: TYPE_TIME
    Dec-06 11:14:32 PM EVENT DEBUG 11:14:32:2853: Queuing Trigger Evaluation: TYPE_TIME Queue size is: 0

    #2
    You might want to post this to the HS3 software forum and not the forum for issues with the Message board as it might not get seen here. Also you mention high CPU, but don't show what is running high and how much is being used so you might want to include those details.

    I would also turn off all extra logging/debugging when checking your baseline CPU so we know where we stand with that turned off.

    Jeff

    Comment

    Working...
    X