Read Write speeds

[blueridgeDSIA]

Im not sure if there is a bottleneck somewhere in my system but I would really like Pi to push my system at least to 75% when it is performing a process.  It does a good job of this during image registration and integration but when I do a batch file conversion for instance or an image container/process container batch process on lets say 200 dslr images, I find that Pixinisght is not pushing my system very hard and it seems to take longer than necessary to complete an operation. 

For example today I converted a big stack of RGB images to Lum and my 960evo m.2 ssd has very high read wrote speeds, but Pi was utlizing less than 25% of the write speed, the cpu and ram were not maxed out.  I dont see a bottle neck anywhere, is there something in the software that limits read/writespeeds?  Could this be user adjusted in Windows?

[pfile]

can a single x86 thread saturate an m.2 ssd? meaning, are disk benchmarks which test maximum disk performance multi-threaded? there's a certain amount of handshaking and queuing going on all up and down thru the memory hierarchy that could limit the performance of a single thread.

rob

[Xplode]

The problem is that Batch file conversion only uses a single thread, i would love to see it upgaded to handle multi thereads since i convert all my files to XISF with compression, i save around 40-50% space and that's a lot with a 250GB+ with XISF files.
I believe it shouldn't be that much work to make it able to run parallel threads on different images

[pfile]

i think the issue is that the javascript engine is single-threaded, thus all PI scripts are single-threaded. that's what i was alluding to in my reply.

rob

[Juan Conejero]

Yes, this is a bottleneck that has to be removed ASAP. I think I can write a C++ version of the format conversion script quite easily. It's in the to-do list with high priority. Thanks for the suggestion.