github BennoBaer-dev/suslik v0.1.1.034
suslik 0.1.1.034

latest releases: v0.1.1.110, v0.1.1.103, v0.1.1.102...
one month ago

Priority per camera. In the camera settings each camera can be set to Low, Mid or High. When events pile up, cameras with a
higher priority are analyzed first.

The CUDA worker is no longer blocked when the first query of the card size fails (GitHub #33). The failure is logged as an error
with its reason, and the size is taken from the next measurement. If the card cannot be measured at all, the worker starts with
one thread and the status is red.

Events without a clip at Frigate are closed as skipped. Alarms are no longer sent for events that started more than 15 minutes
ago.

One log line per page request with route, duration and the slow steps; /health shows the requests in progress.

Remote support: clearing the clip cache and a thread list through the support API.

Known issues, accepted for this release:

  • cuda: on the test notebook the one-time migration of the reference store from 0.1.1.010 took 118.8 s instead of the usual 90 to 93 s. As in 0.1.1.033, the short CPU thread measurement at start-up picked 2 of 6 threads from a noisy timing table, and the migration's CPU step ran with that number. The migration finished without errors; recognition and bookings matched the reference run, and the analysis was not slower. The measured value is stored and reused on later starts; a value for cpu_threads in Settings replaces it.
  • cuda: only the first load test (one compute thread, one live watcher) ran on the test notebook. The second load test (two compute threads) was skipped, because the run stops a machine after a red test.

Don't miss a new suslik release

NewReleases is sending notifications on new releases.