#Performance issues on great hardware?

1 messages · Page 1 of 1 (latest)

jovial locust
#

HASSIO has slowed to a crawl, the webpage takes 5-8 seconds to load anything and my zigbee lights take 7-8 seconds for home assistant to send commands to them.

Running the latest HASSIO through vbox on my linux pc.
Hardware: i3 processor @ 2.10GHz
SSD 120GB
RAM: 2GB
Wired ethernet connection with 1Gbit/s connection.

Not running much on HASSIO itself

  • zigbee2mqtt
  • adaptive-lighting
  • tasmota
  • mqtt broker
  • nginx proxy
  • terminal & ssh (disabled)
  • file editor (disabled)

Been tearing my hair out over this. I'm also very unsure of how to debug the issue.

This all seemed to start happening after I updated to the newest home assistant core and hassio versions two weeks ago. Before this I was using a year old version of both.

I downloaded py-spy as recommended by all the googling I've done. I have lots of logs I can send and can gather any needed debug fairly quickly. Please let me know if you need anything. Glances says python3 is using 93% CPU but it doesn't tell me what addon or integration is running that process.

I've tried the dumb guy normal stuff: stopped all unnecessary addons and uninstalled the ones I didn't need, including integrations. Disabled all non-critical automations and scripts. No dice.

I was planning on just living with this issue until I got around to a reinstall but earlier today I ran into an 'out of memory' issue. Haven't had that issue for over two years!

Does anyone know what could be going on? What should I try next? I'm reading about possible memory leaks in the build from last april - have those been fixed? People are able to run this on a raspberry pi for God's sake even with a clutter of programs why can't I run it on an actual pc?

# 
Collecting samples from 'python3 -m homeassistant --config /config' (python v3.10.10)
Total Samples 35612
GIL: 80.65%, Active: 170.97%, Threads: 24

  %Own   %Total  OwnTime  TotalTime  Function (filename)
 19.35%  19.35%   162.5s    164.0s   _worker (concurrent/futures/thread.py)
 16.13%  16.13%   159.1s    159.1s   do_execute (sqlalchemy/engine/default.py)
  0.00%   0.00%   86.70s    89.70s   run_once (pychromecast/socket_client.py)
  0.00%  70.97%   65.40s    579.5s   _run_event_loop (homeassistant/components/recorder/core.py)
  3.23%  25.81%   35.60s    243.6s   get_sun_events (adaptive_lighting/switch.py)
  3.23%   3.23%   32.20s    34.80s   _loop (paho/mqtt/client.py)
  0.00%   0.00%   29.33s    29.37s   read_events (watchdog/observers/inotify_c.py)
  3.23%   3.23%   26.87s    26.87s   select (scapy/supersocket.py)
  3.23%   6.45%   22.43s    28.43s   __setattr__ (astral/__init__.py)
  3.23%   3.23%   21.40s    21.80s   run (zeroconf/_services/browser.py)
  3.23%   9.68%   20.27s    115.1s   time_of_transit (astral/sun.py)
  0.00%   0.00%   19.47s    19.47s   localize (pytz/__init__.py)
  3.23%   3.23%   19.13s    37.60s   eq_of_time (astral/sun.py)
  0.00%   0.00%   18.43s    18.43s   write (asyncio/selector_events.py)
  0.00%   3.23%   16.97s    30.13s   _sock_connect (asyncio/selector_events.py)
  0.00%  25.81%   16.00s    259.7s   <listcomp> (adaptive_lighting/switch.py)
  3.23%   3.23%   15.87s    15.87s   minutes_to_timedelta (astral/sun.py)
  3.23%   3.23%   14.80s    15.43s   register (selectors.py)
  0.00%  70.97%   14.57s    845.2s   _run (asyncio/events.py)
  0.00%   0.00%   14.47s    14.47s   do_commit (sqlalchemy/engine/default.py)
  0.00%   0.00%   14.47s    14.97s   _wait

running at sample rate 30 (any higher and it gets behind)
This ran for about 10 minutes. Will leave running overnight.

#

part 2 of that debug (I don't have nitro)

(asyncio/tasks.py)
  3.23%   3.23%   13.67s    13.67s   _real_close (socket.py)
  0.00%   0.00%   13.20s    14.07s   fnva (fnvhash/__init__.py)
  0.00%   0.00%   12.97s    31.77s   orm_setup_cursor_result (sqlalchemy/orm/context.py)
  0.00%   0.00%   12.13s    12.17s   unregister (selectors.py)
  3.23%   9.68%   11.03s    72.57s   _async_write_ha_state (homeassistant/helpers/entity.py)
  0.00%   0.00%   10.80s    21.40s   create_task (asyncio/base_events.py)
  0.00%   0.00%   10.67s    16.07s   cascade_iterator (sqlalchemy/orm/mapper.py)
  0.00%   0.00%   10.63s    10.63s   dequeue (logging/handlers.py)
  0.00%   0.00%   10.50s    10.50s   julianday (astral/sun.py)
  0.00%   0.00%   10.23s    31.73s   validate_mapping (voluptuous/schema_builder.py)
  0.00%   0.00%    8.80s     8.80s   hour_angle (astral/sun.py)
blazing lodge
#

are you running 2023.3.2 ? I started having performance issues after going from .1 to .2, reverted back and all seems fine so far...

jovial locust
#

I can try that but would like to debug 2023.3.2 to help out the devs

#

Is it relatively easy to revert? Honestly seems like a last ditch effort

blazing lodge
#

yeah just go under the backups and revert

jovial locust
#

3.3 is available, maybe I'll try that.

jovial locust
#

Updated and noticed it's a bit faster, not much. Allowed an extra gig to hassio's ram, so it's now at 3GB. Here's some output:

# 
➜  ~ ps aux
PID   USER     TIME  COMMAND
    1 root      0:16 /sbin/docker-init -- /init
    7 root      0:00 s6-svscan -t0 /var/run/s6/services
   36 root      0:00 s6-supervise s6-fdholderd
  834 root      0:00 s6-supervise stdin
  836 root      0:00 s6-supervise ttyd
  837 root      0:00 s6-supervise sshd
  840 root      0:00 bash /usr/bin/bashio ./run
  844 root      0:00 sshd: /usr/sbin/sshd -D -e [listener] 0 of 10-100 startups
  888 root      0:04 {tmux: server} tmux -u new -A -s homeassistant zsh -l
  889 root      0:03 zsh -l
 1150 root      0:00 ttyd -d1 -i hassio -p 62866 tmux -u new -A -s homeassistant zsh -l
 1163 root      0:00 sshd: hassio [priv]
 1165 hassio    0:00 sshd: hassio@pts/0
 1166 root      0:01 -zsh
 1201 root      0:00 ps aux
➜  ~ free
              total        used        free      shared  buff/cache   available
Mem:        3043676     2903124       46748        3112       93804       92516
Swap:        760916      760896          20
jovial locust