Whew getting tricky eh! Thanks everyone for keeping at it
Updated bios, checked settings, and verified all cores are working correctly for other apps (hit 100% in prime95, 60% in BF4). Qimage doesn't seem to be using even 1 core fully - 5-10% usage typical, so even a full 25% that a full core would utilize would be a big boost. I'm wondering if its a RAM issue? TerryM is qimage actually using 30% or your RAM? The 50MB average I'm seeing seems really low...
Qimage analyze current settings found nothing.
These 3 tests all run with identical settings to the initial tests @ 300dpi except the final vector test for comparison with Fred's single image test times as I didn't know what his setting was for his 3min reference: The surprising bit for me was the single image scale test taking substantially longer than the 3 tiled images with the same settings:
3 images, x1 ea, tiled on a single 44x47 page, Fusion 5min
Single image from same job scaled to fill 44x47 page, Fusion 20min+
Single image from same job scaled to fill 44x47 page, Vector 6min
"Off-Line" = paused windows print queue to prevent test from printing. Identical results with "live" printer & printer connection is gigabit ethernet. This should only be an issue during actual printing, not during qimage's processing stage, as no data is sent to printer until after qimage has finished up.
"slow" has no direct basis for comparison, It just felt slow compared to what I remember from my old shop where I was running older workstations, and when I saw the resource use that really got me wondering if something was awry...