jpmens
commented
13 hours ago approx 141k lines in its .rec file
that's quite a lot...
If you use Frontend to select a short time span, do you likewise experience the high CPU load on the Recorder machine?
I'll preface this by saying that I'm not entirely sure if this is a frontend issue or a recorder issue, but I'm leaning towards recorder so I'm reporting it here.
Behavior: When using the OwnTracks Frontend, the UI stays on "Loading data, please wait…" for many minutes at a time. While this is happening,
ot-recorderon the server has very high CPU usage—typically it's pegged at 100%. After several minutes, the "Loading Data" UI element disappears from the client browser, but no new data is shown on the Frontend map. It seems to be timing out, I think?Expected Behavior: The Frontend will load data from the server and display it, and the recorder backend will retrieve and present data to the API in enough time to prevent a timeout.
Test Setup: 2x processor, 2GB RAM, SSD-backed storage VPS (from RackNerd; pretty standard KVM Linux VPS), running Debian 12. Used exclusively for OwnTracks. Very little else installed. OwnTracks was installed/configured using the
quicksetupAnsible scripts, and it's running recorder 0.9.8, frontend 2.15.3. Data is about one week's worth of location information from 3 devices; two devices were in Significant mode most of the time, one was in Move mode most of the time. Ping times from the client to the server are about 215 ms (min/avg/max/stddev = 205.382/215.504/276.041/20.332 ms).Data seems to be correctly recorded to the backend files—running
tail -fon an active device's .rec file (inside/var/spool/owntracks/recorder/rec/username/devicename/) shows entries being added periodically by devices. The device with the most recorded data (the one in Move mode most of the time) has approx 141k lines in its .rec file.The 'ot-recorder' Systemd service is reported (via
systemctl status) as "active (running)" with an uptime of 6 days, 514M of memory and 1 task. Themosquittoservice is also running; uptime 6 days, 37M memory, 1 task. Andnginxis running, but with a shorter active time (only about 15 hours) and 4.6M memory. I'm unclear whether the 514M of memory usage byot-recorderis normal or represents some sort of memory leak.I don't think this is a particularly slow or underpowered VPS. As a rough benchmark, it runs
tar -cvzf test.tgz quicksetup(compressing thequicksetuprepository checkout) in 0m0.065s real. Happy to run some better benchmarks if raw compute horsepower is potentially the problem.