MobileRead Forums - View Single Post - calibre-parallel.exe on WinXP makes working impossible, why not change priority?

Jackie7 · 07-15-2011, 12:17 PM

Hi,

this has been posted on the bugtracker several times, it has been marked as "fixed" each time, but it is not fixed!

The problem is that the process called calibre-parallel.exe is started multiple times, i assume depending on the CPU cores. Nothing bad about that, but the problem is, that it is always launched in Normal-Priority under Windows XP, which makes working on a compouter while converting 200 ebooks or so completely impossible, at least on my Intel E6600 with 4GB of RAM. Very annoying.

Of course, you can manually set the priority of calibre-parallel.exe in Taskmanager or ProcessExplorer to "Below" or "Idle", but it is reset each time a new job is started.

Why isn't it possible to select a default priority at which this process works in Calibre, thus making working with the computer still possible? Many users seem to have this problem, but unfortunately, the developers don't care, or they don't get the point, I don't know, but it would be really nice if this could be fixed.

07-15-2011, 12:17 PM	#1
Jackie7 Enthusiast Posts: 31 Karma: 10 Join Date: Jul 2011 Device: Kindle 3	calibre-parallel.exe on WinXP makes working impossible, why not change priority? Hi, this has been posted on the bugtracker several times, it has been marked as "fixed" each time, but it is not fixed! The problem is that the process called calibre-parallel.exe is started multiple times, i assume depending on the CPU cores. Nothing bad about that, but the problem is, that it is always launched in Normal-Priority under Windows XP, which makes working on a compouter while converting 200 ebooks or so completely impossible, at least on my Intel E6600 with 4GB of RAM. Very annoying. Of course, you can manually set the priority of calibre-parallel.exe in Taskmanager or ProcessExplorer to "Below" or "Idle", but it is reset each time a new job is started. Why isn't it possible to select a default priority at which this process works in Calibre, thus making working with the computer still possible? Many users seem to have this problem, but unfortunately, the developers don't care, or they don't get the point, I don't know, but it would be really nice if this could be fixed.