A weird question, but since there's another article on HN right now about programming language energy efficiency https://news.ycombinator.com/item?id=24816733 any idea whether going from 9fps to 1840fps consumes the same power, 200x the power, or somewhere in between?
I see Rust is almost equal to C if not better in the graph, however, I think equally-skilled programmers in either language would show the Rust programmer spending more 'energy' programming and iterating than the C programmer, but then make the argument that the C program will use more 'energy' downstream if bugs slip in. In any case, an eye-opening metric on what I, and I am sure many, take for granted. Cool.
Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
21–30 of 58 posts
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#22Out of curiosity, what are the possible use cases for object detection at >100 fps? I assume it would have to be objects that move very fast, i.e. nothing ordinary that I can think of. [edit] actually stupid question. I assume it's more about throughput than fps, i.e. be able to process lots of streams on the same machine, for instance for doing mass analysis of CCTV streams.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#23Out of curiosity, what are the possible use cases for object detection at >100 fps? I assume it would have to be objects that move very fast, i.e. nothing ordinary that I can think of. [edit] actually stupid question. I assume it's more about throughput than fps, i.e. be able to process lots of streams on the same machine, for instance for doing mass analysis of CCTV streams.
While I'm not into object detection such as this, I can easily imagine this being part of a system where you want the rest of the system to have time to act on the information. As such the point isn't that you can detect objects >N fps, but rather that the object detection shouldn't take more than X% of the time per cycle so that the overall cycle time can run at a given rate.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#24Out of curiosity, what are the possible use cases for object detection at >100 fps? I assume it would have to be objects that move very fast, i.e. nothing ordinary that I can think of. [edit] actually stupid question. I assume it's more about throughput than fps, i.e. be able to process lots of streams on the same machine, for instance for doing mass analysis of CCTV streams.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#25Earlier quoted context omitted.
Self-driving. Ideally you want something around 1000fps and low latency, so it has time to react. I'm sure military and sports applications are obvious too.
Doubt Humans reaction times are much slower than that. In fact for some things it can take a whole second https://www.visualexpert.com/Resources/reactiontime.html Maybe racing sports have shorter reaction times, but I'd be frankly surprised if it was something 10fps for your average drive should be more than enough
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#26Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#27Out of curiosity, what are the possible use cases for object detection at >100 fps? I assume it would have to be objects that move very fast, i.e. nothing ordinary that I can think of. [edit] actually stupid question. I assume it's more about throughput than fps, i.e. be able to process lots of streams on the same machine, for instance for doing mass analysis of CCTV streams.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#28Any word on latency? I didn't see anything in the article. I guess, since this is a synthetic test just pumping a single image file through repeatedly instead of an actual video stream, then it wouldn't realistically be measurable. But if latency is particularly low, this would be a boon for AR systems.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#29Out of curiosity, what are the possible use cases for object detection at >100 fps? I assume it would have to be objects that move very fast, i.e. nothing ordinary that I can think of. [edit] actually stupid question. I assume it's more about throughput than fps, i.e. be able to process lots of streams on the same machine, for instance for doing mass analysis of CCTV streams.
For me it's only exciting because it lowers the barrier of how much I can do with a much smaller system than double 2080ti's.
Re: Object Detection at 1840 FPS with TorchScript, TensorRT and DeepStream
#30How portable are these techniques to other architectures? Could >100 FPS be realistically achieved today using only CPUs or mobile phones?