A
Alan Browne
I recently bought a new computer with a modest Athlon 64X2 4200+ dual core.
Setting the affinities so that the OS assigns the CPU cores results in
both processors running at about 50-60% during the scan (even while
editing in PS [odd angle rotations]):
5:30 (M:ss) for the scan.
I set the Dimage s/w to use core 1 and Photoshop to use core 0.
Time to scan a 35mm slide @ 5400 dpi (16 bit, ICE + GEM on, Firewire):
14:30 (MM:ss). So, at least for scanning, there is no benefit (quite
the contrary) to assigning each process to a specific core.
What's really nice: while scanning and working in PS, there are no
pauses or slowdowns of the scan and PS works pretty fast (as if nothing
else is going on).
A nice way to work...
Cheers,
Alan.
Setting the affinities so that the OS assigns the CPU cores results in
both processors running at about 50-60% during the scan (even while
editing in PS [odd angle rotations]):
5:30 (M:ss) for the scan.
I set the Dimage s/w to use core 1 and Photoshop to use core 0.
Time to scan a 35mm slide @ 5400 dpi (16 bit, ICE + GEM on, Firewire):
14:30 (MM:ss). So, at least for scanning, there is no benefit (quite
the contrary) to assigning each process to a specific core.
What's really nice: while scanning and working in PS, there are no
pauses or slowdowns of the scan and PS works pretty fast (as if nothing
else is going on).
A nice way to work...
Cheers,
Alan.