Quote:
Originally Posted by oldbwl
One reason why I wanted a timeout too was that, there e.g. there can be 4 threads running simulataneuosly (one per core?), On the 1st job the conversion of the book started to take ages, then another and so on until all Job threads were in use.
|
If all cores were in use then you had multiple books being converted and they were all taking long. If you noticed it taking a long time then open the jobs window (clicking on jobs in the lower right corner) and stop the one job that is holding you up, then restart that book conversion when you have time.
Quote:
Originally Posted by oldbwl
I had many other tasks, they did not get done by when I needed them. 2 were really important. I know I could prioritise the order but a failsafe timeout would be great.
|
Were the other tasks books being converted? If they weren't books being converted then you can prioritize all other tasks by going to Preferences - Behavior and changing Job priority to low.
Quote:
Originally Posted by oldbwl
True, so if I restricted it to 1 thread, does that mean a job will share all avail cores? or will the CPU have one in use and 3 idle?
|
No, I believe it is one job, one core.
Quote:
Originally Posted by oldbwl
these jobs lasted over 10 hours
|
If these books are your creation then save them out of Word as html filtered and the conversion time will drop drastically.
Quote:
Originally Posted by oldbwl
The CPU gets real hot on these long jobs evidenced by the fan kicking in on high rpms, so there is another reason to desire this facility.
|
The fan / cpu settings are by design. This is a hardware issue, if you don't want your CPU running as configured then tweak the Bios so it runs slower. If it used to run cooler then buy a can of air, open it up and spray out the dust that has accumulated.