15 ms·
> One practical detail is worth knowing. The new engine is CPU-only at the moment, so if you select a non-CPU backend and target (for example CUDA or OpenVINO t
by ftchd 4mo ago
> One practical detail is worth knowing. The new engine is CPU-only at the moment, so if you select a non-CPU backend and target (for example CUDA or OpenVINO through setPreferableBackend and setPreferableTarget), you will want the classic engine.
So there's room for even better performance!
- wongarsu 4mo agoIt's certainly a choice to make your headline feature a new ONNX engine, feature a bunch of comparisons how it's better than ONNXRuntime, while casually mentioning on the side that the cool new much faster engine is CPU-only Sure, running models on the CPU is very much a thing in computer vision (the benchmarked YOLOv8n has 37M params). But this whole announcement feels more like OpenCV catching up to the modern world, not "The Biggest Leap in Years for Computer Vision" Still great, needing fewer libraries is a good thing, but maybe a bit oversold
- VadimPR 4mo agoThe release post is AI-written with little human oversight and it shows.
- vdfs 4mo agoThe illustrations couldn't be any more generic-ai
- kphorn 4mo agomy code, my commit - ugh
- claytongulick 4mo agoI had to stop reading after: "This is not just another incremental release. OpenCV 5 is a major step forward." If a human can't be bothered to write a piece, I can't be bothered to read it.
- VulgarExigency 4mo agoThe endless deluge of AI prose really wears on the soul once you start noticing it.
- thin_carapace 4mo agoi initially adopted this line of thinking. after exposure to arguably valid cases like translated articles, it now seems to me that the most efficient path forward (after first noting AI prose) is to scan past all language and evaluate whether or not useful content is encoded within. theres no benefit to anyone (except those benefitting from societal atrophy) in wasting brain cycles on unnecessary verbosity, however blanket rejection necessarily involves loss of valuable information.
- danjc 4mo agoIt's not just annoying, it's tiring
- kphorn 4mo agoI think the only thing that the human did was remove the emdash between the two sentence fragments and replace with a period.
- dismantlethesun 4mo agoI felt that this was an indication that OpenCV had finally discovered SemVer.
- trklausss 4mo agoThis is what I hate about AI. Not that people use it, it's great to accelerate specific workflows, make less mistakes etc. It's just blindly trusting it and just saying "Make a post about a CV library release, make no mistakes" and calling it a day. Where is the human creativity in writing release notes gone?
- nnevatie 4mo agoNo one uses ONNXRuntime (nor the new engine in OpenCV 5) in production. For anything performance-sensitive, one would run models under TensorRT, as an example.
- gunalx 4mo agoProduction dosent have to be performance sensitive, so devex may still outcompete the performance differences in some scenarios.
- snovv_crash 4mo agoStrong statement to make when I have at least 2 datapoints contradicting it, in SaaS and embedded/robotics.
- amorroxic 4mo agoCurious on what backs this assertion. As a counterpoint we’ve been running 200+ models in production for more than 5 years - language models, embedding, classifiers, low tens to hundred M params. Traffic in the order of 1-2M requests/day and everything is enabled by onnx with some cgo (or Rust) plumbing on top. What’s your SLA?
- nnevatie 4mo agoAhh, I should have probably added some context around my hyperbole. I was referring to real-time computer vision - think of e.g. segmenting FHD/UHD video.
- pzo 4mo agohow are supposed to use TensorRT on iOS, iPadOS, Android or even Web? Production is not only cloud.
- OvervCW 4mo agoYou can use ONNXRuntime with a TensorRT backend, so one does not exclude the other.
- antonvs 4mo ago