IReallyLikePizza2
Known around here
Hopefully with time they get it sorted out, if I could have 6-8% idle with GPU doing the rest, I'd be very happy
v4.1.0
is released.v4.2.0
fixes an outstanding issue with the systems log page using too much memory over time and crashing the browser. it also pre-loads 500 lines of logs on page load now and keeps 500 lines of text on screen, flushing old logs from the UI.how big is your rekor agent's db? how many plates are you seeing a day?I think I underestimated the disk space usage of 28,000 plate images. Are you able to add disk usage into the UI? I guess some sort of stat page.
I have 'openalprwebhookprocessor' within a local volume since it does have a database (didn't want to cause lock issues using over NFS or CIFS). Wonder if it might end up being best to have a volume mount so the images can just be stored on an NFS volume. My processor.db is currently 36 GB.
This is what I'm thinking I will do to. I don't think I need Rekor to hold 40GB and then have the webhook hold a duplicate 40GB. I also backup my VM daily so I have backups I can always revert to if something screws up.Rekor's plateimages db is 41 GB. I get 250-300 plates/day (should be images since ~July when I started). I already run backups on the server where Rekor scout runs, so the database is backed up on a daily basis. Maybe have a setting to just keep the last X days of images within processor.db? I don't know what's best in this case.
[]
. Not sure what that means. Why is that link up there and how is it different from the scrape in the agent page? I assume it's just to quickly grab the last 24 hours worth of plates and no more.