0.93: Batch convert + "Use CPU Cores" very slow to start with 30,000 images
Posted: Mon May 20, 2019 12:25 am
XnView: MP 0.93 - 64 bit
OS: Windows 10 1809 - 64bit
Computer: Dell XPS 9550 laptop (Intel i7-6700H @ 2.6 GHz, dual GPU - NVIDIA GTX 960M / Intel HD Graphics 530)
XnViewMP becomes unresponsive for (5+ minutes) when doing batch convert and "Use CPU Cores"
For input files, I am using TIFF (LZW compressed) images. For output I am using JPEG-XR. I have tried different output formats and still the same... if I don't tick "Use CPU Cores" then XnViewMP starts batch convert immediately.
See screenshots below:
To reproduce:
1. Highlight 30,000+ images, right-click > Batch Convert
2. Tick "Use CPU Cores", I set to 4. Click Convert
Actual behaviour (bug):
XnViewMP becomes unresponsive for a long time, eventually it starts batch convert.
Expected behaviour:
XnViewMP should start batch convert immediately.
If this can be looked at that would be great, I really like the fast performance of "Use CPU Cores" but the pre-delay seems to be longer when more images are used (I tried with 500,000 images and I waited for 30 mins, still XnViewMP was unresponsive)
OS: Windows 10 1809 - 64bit
Computer: Dell XPS 9550 laptop (Intel i7-6700H @ 2.6 GHz, dual GPU - NVIDIA GTX 960M / Intel HD Graphics 530)
XnViewMP becomes unresponsive for (5+ minutes) when doing batch convert and "Use CPU Cores"
For input files, I am using TIFF (LZW compressed) images. For output I am using JPEG-XR. I have tried different output formats and still the same... if I don't tick "Use CPU Cores" then XnViewMP starts batch convert immediately.
See screenshots below:
To reproduce:
1. Highlight 30,000+ images, right-click > Batch Convert
2. Tick "Use CPU Cores", I set to 4. Click Convert
Actual behaviour (bug):
XnViewMP becomes unresponsive for a long time, eventually it starts batch convert.
Expected behaviour:
XnViewMP should start batch convert immediately.
If this can be looked at that would be great, I really like the fast performance of "Use CPU Cores" but the pre-delay seems to be longer when more images are used (I tried with 500,000 images and I waited for 30 mins, still XnViewMP was unresponsive)