You have posted at various time ADSimDetector beanchmarks. Historical values from a PDF that I am looking at now being about 485 FPS for a 1024 x4 1024 image. If I increase this image dimensions to 3078 by 4096, basically 12 times the data, the frame rate drops by about the same factor of 12 down to 40 FPS or so (This is confirmed using one of your old AD1.9 windows prebuilts and playing with image sizes). This FPS value is pulled from at the very top level NDStdArray plugin, blocking, so frames are not dropped.
In AD3-0, This plugin is multi-thread enabled. I’m assuming that if someone did not specify a value, 1 thread is allocated for this plugin and that more *might* make it handle bigger data or faster data. I.e., 5 threads might make that original 1024 x 1024 image collect at . . . 2400+ FPS . . . and that larger image perhaps 200 FPS without dropping frames.
Or am I mistaken on how the AD3.0 threads work?
I have a newer model Xeon computer with 12 real cores, most of which are idle at any given moment, and was wondering which plugins may be worth committing cores to.