Mike Chaney's Tech Corner
November 16, 2024, 11:52:49 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Qimage registration expired? New lifetime licenses are only $59.99!
 
   Home   Help Login Register  
Pages: [1] 2
  Print  
Author Topic: Ultimate only using 1 core on i7 5720k machine  (Read 16378 times)
Chris
Jr. Member
**
Posts: 60


« on: May 07, 2016, 02:08:08 PM »

As title only 8 to 10% of processors capacity is being used while printing.  I've checked the processor affinity in task manager and it shows all cores are selected (windows 10). I've tried all variations of multi processors setting have been tried in qimage, looking for ideas as to how to resolve issue.
Sorry for abrupt post but I'm sat in a field trying to type this post in between photographing horses going past me every 2 mins :-)
Thanks
Logged
Fred A
Forum Superhero
*****
Posts: 5644



WWW Email
« Reply #1 on: May 07, 2016, 02:52:51 PM »

Quote
As title only 8 to 10% of processors capacity is being used while printing.  I've checked the processor affinity in task manager and it shows all cores are selected (windows 10). I've tried all variations of multi processors setting have been tried in qimage, looking for ideas as to how to resolve issue.
Sorry for abrupt post but I'm sat in a field trying to type this post in between photographing horses going past me every 2 mins :-)
Thanks
Chris,
If I take your question literally, that Q image is showing less than 10% CPU usage while printing, that would be normal.
Qimage has nothing to do at all after the processing is done and the file is sent to the spooler. The CPU drops off to almost nothing especially while the printer is printing.
The computer is running the show, and feeds data to the printer as fast as the printer can use it.

Fred
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #2 on: May 07, 2016, 03:11:36 PM »

Whoop's, I meant when I hit the print button and it starts to process the queue  Shocked
Logged
Fred A
Forum Superhero
*****
Posts: 5644



WWW Email
« Reply #3 on: May 07, 2016, 03:26:51 PM »

Hi Chris,
I really don't know how I could tell how many cores/threads were being used at any given moment except for timing.
First of all, see my attached screen snap and see if you have your multi cores turned on in Qimage.
If not, turn them on...
If they are alrady turned on, time how long it takes to complete the processing.
Then set it to 1 core, and time it again.
See what you get.

Fred
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4218



Email
« Reply #4 on: May 07, 2016, 03:27:45 PM »

Let's start with the basics.  Look at the splash screen when first starting QU.  How many cores does it report on the splash screen?  It should report 8 for an i7 5720.

Edit: that splash screen is a good indicator because the number of cores is the number of threads it will spawn for printing (provided you have multi-threaded printing set to auto or 8 ).

Mike
« Last Edit: May 07, 2016, 03:33:34 PM by admin » Logged
Chris
Jr. Member
**
Posts: 60


« Reply #5 on: May 07, 2016, 03:45:40 PM »

Qimage recognises 12 cores on start up screen.
I've tried all the setting on the print processing screen and done test and they all take the same time (task manager indicates activity on one core only)
I a mentioned previously task manager also shows that all 12 cores should be used for qimage (affinity settings)
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4218



Email
« Reply #6 on: May 07, 2016, 03:57:34 PM »

Well that's the strange part.  If it says 12 cores on the splash screen and you have multi-threaded printing set to "Auto", it's going to spawn 8 threads.  At that point, we're down to the operating system not allowing but one core.  Since 8 threads are running, it's up to the OS to assign them each a core and if it's only using a single core, something is preventing that.  Normally that's controlled by the affinity, but I've seen cases where something in the shortcut may cause that.  Are you starting it from a desktop shortcut?  Maybe try deleting the shortcut and then reinstalling QU so it creates a new one.

Mike
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #7 on: May 07, 2016, 04:11:16 PM »

Yes I'm starting it from the desktop shortcut, I'll delete/reinstall it as soon as I get back to the trailer.  I'm trying to come up with things to try when I get back, my wife is pulling her hair out as she is having to do all the printing while I lounge around in a field taking the photos :-)
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #8 on: May 08, 2016, 10:33:24 AM »

Thanks for the suggestions,. Nothing has worked though.I've uninstalled it and reloaded with new shortcut, I've also tried starting from the .exe file.with no difference in processor usage.  Any other ideas??  Huh? Huh?
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4218



Email
« Reply #9 on: May 08, 2016, 12:14:48 PM »

Knowing that QU is running 8 threads, we're down to the system/OS not assigning them properly.  The only other thing I can think of is going to MSCONFIG and the boot options, advanced, and making sure "Number of Processors" is NOT checked.  Might want to check multi-core options in your BIOS as well.  Also, try running another CPU intensive app like a video editor to produce a video, or maybe a video converter.  Since all multi-threaded apps work basically the same way (by just spawning multiple threads), if other apps are using multiple cores and QU is not, then something is is making app specific settings to set QU to one core specifically.  At that point, you need to look at app/shortcut settings or consider the possibility that something like an antivirus program is interfering.  Since you've checked affinity and found all CPU's checked, I'm leaning toward the probability that all apps on your system are limited to a single core.

Mike
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #10 on: May 08, 2016, 12:55:24 PM »

I've.just tried the msconfig setting before you replied,.it didn't make a difference (box was unticked already, also tried it with 12 cores enabled) Cry
Other apps are using all cores fully.  I'm going to try the BIOS next, thanks for the ideas
« Last Edit: May 08, 2016, 12:59:00 PM by Chris » Logged
admin
Administrator
Forum Superhero
*****
Posts: 4218



Email
« Reply #11 on: May 08, 2016, 01:58:44 PM »

You should probably run another multi-threading test in QU too.  Go into a folder with a bunch of images (say 25 or more, preferably raw photos), and use "View", 'Rebuild Thumbs".  See if more than one core is being used while it is building thumbs and the problem is confined just to the printing part.

Mike
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #12 on: May 09, 2016, 08:33:19 AM »

Just tried changing settings in BIOS, no difference to print CPU usage.  Tried creating thumbnails and qimage uses up to 75% CPU, so it can use more CPUs but isn't when processing the print queue??
Logged
Chris
Jr. Member
**
Posts: 60


« Reply #13 on: May 09, 2016, 09:55:01 AM »

OK update, tried printing to a different printer (12x8 dye sub and CPU usage is higher (up to 37% usage with multiple cores, though one core appears to be doing most of the work) but when I set interpolation to OFF it reverts to only using 1 CPU core (this is the setting that I've been using on the other printer (6*8 dye sub) as it was always the fastest in qimage studio).....
I've now tried this in the original printer and the same thing happens (CPU peaks momentarily at 24%).
Core 6 seems to be doing the majority of the work and interestingly when editing an image with qimage this is the only core that appears to be used (I've tested using the rotate function as this always slowed my old computer down). Is qimage meant to use multiple cores when editing images??

Edit..when printing to file qimage is again using about 9% CPU (1 core is showing usage)

Thanks again for the help
« Last Edit: May 09, 2016, 10:27:25 AM by Chris » Logged
admin
Administrator
Forum Superhero
*****
Posts: 4218



Email
« Reply #14 on: May 09, 2016, 01:01:44 PM »

Wow, I didn't even think to ask you if you had turned off interpolation.  It's the interpolation that runs on multiple cores so if you turn it off, there's nothing to multi-thread: it just sends chunks of the image to the driver so no need to multi-thread that.  So that explains it.  In the editor, only the USM/DFS sharpening is multi-threaded.  QU only multithreads the time intensive operations like thumb building, raw cache building, and printing.  USM/DFS sharpening will use up to 4 cores because that operation is computationally expensive and is used in multiple areas of QU.

Mike
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Security updates 2022 by ddisoftware, Inc.