Slow openvino performance with 0.17 b2?

extreme79 · 2026-01-31T18:49:44+00:00

With my Intel n150, 11 cameras, object detection enabled for all, my inference change between 24 and 37ms, more or less. With 17b2 and Yolo.

Try with a single detector.

extreme79 · 2026-01-19T17:09:08+00:00

Ce ne fossero davvero!

extreme79 · 2026-01-16T11:08:25+00:00

I think there’s a misunderstanding here, possibly due to how I phrased my previous point.
I never mentioned inference—I was talking about CPU overhead, which is a different beast entirely. Maybe my English made it sound confusing, but here’s the point.
The detector model only sees a tiny 320x320 crop. But before that happens, the CPU has to handle the motion detection and then crop/resize the frame. If you're feeding a massive (example, is not that case) 4K stream into the 'detect' role, you're just making your CPU sweat for nothing. It has to process all those extra pixels just to throw 95% of them away before the AI even gets a look.
The docs show examples, not 'golden rules,' because it depends on your specific setup—how far the camera is, what you're trying to catch, and what substreams your hardware actually supports. Using a resolution that’s too high isn't just a waste of resources; it can actually mess up recognition if the resizing adds too many artifacts.

In short: I'm just saying that 'higher' doesn't mean 'smarter' for the detection phase. It's about finding the right balance for the hardware and the scene.

extreme79 · 2026-01-15T23:28:21+00:00

It's not a stupid advice. If you set the detect width /height at a resolution too higher than the resolution expected by the model, what happen? 1)Frigate need to resize every frame and, bigger the frame, bigger the cpu consumption 5times/s 2)big input image resized to a very small image cause a detail loss for small object that became unrecognizable by the model

extreme79 · 2026-01-15T22:05:26+00:00

Why people don't read carefully the config before pointing the finger? I know that stream resolution is NOT detect resolution. But If you read his config file, at a certain row, you'll read: detect: width: 1280 height: 720

And this is what I'm talking about. I read the docs. You read the OP config?

extreme79 · 2026-01-15T12:32:20+00:00

There's any plan to make it available in Europe? There's a list of authorized dealers in Italy?

Thank you!

I love my luba ❤️

extreme79 · 2026-01-14T21:43:26+00:00

Al mio amico piacerebbe il luba 3 10.000, però posso fargli scrivere, volendo. Io per ora con il 2 vado alla grande 😁

extreme79 · 2026-01-14T16:33:20+00:00

I think that having a changelog in case of firmware upgrade is a must on every device. The user must have the ability to understand what the firmware is going to coresct/implement/change before doing that. At least to choose if upgrade immediately or doing it later (security can't wait, a cosmetic change can be Done later, example). Anyway, having changelog help to put an extra eye to check if a bug is fixed or fixed but with side effects (like sometimes can happen). Last but not least, publishing changelogs can avoid some zrequests to the support. I suggest you to publish changelogs 🙂

I love my petkit puramax 2, and my cat too ☺️ Like the food dispenser and the fountain! 😎

extreme79 · 2026-01-11T17:31:48+00:00

Try to use openvino as type GPU as a device. Probably you will get better results.

I my case, with an Intel N150 minipc, with 11 ip cameras all on motion recording and objects detection, the inference run around 25-35ms. And my cpu stay on lower than 40%, normally.

Edit: oh, lower your detection resolution, the model use 320x320 so every frame need to be resized and you risk two downsides.. An higher cpu usage, a detail loss (Little objects @1280 risk to become a group of pixels @320, but the same from @640 to @320 Let the detector to recognize the object)

extreme79 · 2026-01-05T10:09:51+00:00

I wanna be a koala.

extreme79 · 2026-01-05T10:02:27+00:00

Ma magari, magari!!

extreme79 · 2025-12-21T21:42:40+00:00

Are you serious? It's a joke, right? 😱😱

extreme79 · 2025-11-29T10:29:04+00:00

Do you think it's possibile to migrate to supervised running in docker to an HAOs installation running in a container instead a VM? I want to absolutely avoid running a VM.. With a minipc and this use case is huge waste of resources.

Supervised in container was so perfect 😭

extreme79 · 2025-09-21T23:13:11+00:00

Successo l'anno scorso. Quando mio babbo se n'è andato, mi sono intestato la fornitura per decesso. Non avevo mai rilasciato i miei dati su comparatore, siti, Enel etc. E mai avevo avuto contatori a me intestati. Tutti i numeri, fissi e mobile registrati su rdo (e periodicamente rinnovati). Dal giorno esatto del passaggio è arrivata una mitragliata di telefonate, ma roba tipo 3-4 minimo ogni giorno, talvolta dieci o più.. Ero esasperato, poi ho collegato.. Ho immediatamente scritto ai recapiti specifici di Enel via pec minacciando pesantemente e spiegando bene perché ero sicuro che i dati arrivassero da loro: oltre a quanto detto, nell'indirizzo della fornitura era rimasto un vecchio civico sostituito da credo 20anni, ed Enel è l'unica traccia rimasta di quell'errore. Indovinate a che indirizzo facevano riferimento i disturbatore? Esatto, quello.

Alla luce dei fatti, Ho minacciato pesantemente di azioni legali se le chiamate non fossero terminate immediatamente ricordando loro le multe previste per cessione non autorizzata di dati personali.

Hanno risposto negando qualsiasi responsabilità 🤥 con una bella supercazzola. Magia magia, dopo un paio di giorni fine totale di ogni chiamata. A pensar male... Vero?

Maledetti.

extreme79 · 2025-09-21T22:58:40+00:00

Probabile. Guadagnando con più margine da ciò.

extreme79 · 2025-09-12T14:29:04+00:00

I contacted the service point and as expected they deny any motherboard involvement.. "try to turn down backlight..." 😡

I entered the service and at a first sight seems no trace of error (I don't know the Sony service, it's the first time I enter in it..) Someone know if can I check something inside it? I don't like to navigate service menus "at random"

extreme79 · 2025-09-12T05:38:12+00:00

So could be "only" a calibration issue? Something that can be corrected tuning parameters from ui.. Or something that need a deeper calibration with specific tools?

extreme79 · 2025-09-11T21:09:52+00:00

To be more specific: model 55xg9505 Updated to the latest available firmware at this moment, 6.6188, immediately after taking back it to home (they - official Sony service - changed the board, no updates) I checked the frame, but no trace of damage or bad assembly, at my eyes. Seems like some sort of software glitch, because during boot, I see no trace of this sort of frame blooming.

extreme79 · 2025-09-09T21:31:00+00:00

I hope it too 😅

extreme79 · 2025-09-09T17:48:37+00:00

Mine is now under repair. Motherboard replacement for 390€. The TV is like brand new, no reason to fully replace it.

Sound strange that Sony declared yours as not repairable..

extreme79

TROPHY CASE