forum

Hej,

I have upgraded my Raspi3 (4core, 1MB RAM) to Buster and z-way 3.01.
After a couple of tries this finally works, but performance is really bad.

Using the GUI, I'm getting "Request failed..." or "Connection refused by the z-way-server" many times, response times are quite bad (not ms, more seconds or minutes), etc.... The attached monitoring solution (icinga) complains much about the same issues.

Checking on the process status, I can see 9 sub-processes/thread under the main (see attachment).
One process is doing the main stuff (almost 80% of one core), one other is also working, but using just 50% of the proc time of first process ... and all other threads are doing almost nothing !

Another minor thing is that the z-way-server is not starting directly after a reboot (status running(exited)). I always need to stop and start it with systemctl. Anyway, this doesn't matter if the performance issue is not solved, as I rather think to move to OpenHAB instead.

Have anyone else these performance issues ?
Any hints how to solve this ?

BR

The process should never reach more than 10% except for short peaks. So this is not normal.

What have you confirugred as home automation ? How many requests per second do you have?

Main thread is an idle loop, so 80% for it means some problem us happening. There is nothing but a wait loop in this thread.

May be let us debug it or attach strace/gdb to check what is the thread doing.

Hi,
can you check with "top" the write processes?
pressing "1" you see all the kernels and the "wa" state (waiting for I/O).
Something like this:
Maybe Pi is swapping (something else installed?)?

Michael

Hej,
seems I had some problems with low voltage.

"vcgencmd get_throttled" gave me 0x50005, "vcgencmd measure_clock arm" was 600mhz and "vcgencmd measure_temp" 62C.

After changing the power device and the USB power cable, "throttled" changed to 0x0 and, sometimes 0x80000 (soft_temp).
Setting temp_soft_limit=65 (default 60) in /boot/config.txt, temp throttling (down to 1200GHz) is little less now as well.

Anyway, I still see peeks (60-80%) for just one thread and the others doing almost nothing, but there are also periods with 2-4%.
The GUI is performing and responding better, not perfect but sufficient.
At least I was able to enable my Tasmota devices again and the icinga monitoring looks better too now.

If you still wanna have performance and debug data, send me an email about what you need.

@michap: No swapping.

@dirkh - and what about "the "wa" state (waiting for I/O)." ?

Michael

WA state is alomost zero for each core.

Just if z-way-server wanted to read from its module, I can see short peeks there.
Somehow expected.