Advanced search

Message boards : Number Crunching : How many cores will one WU use?

Author Message
GLeeM
Send message
Joined: 1 Jul 13
Posts: 118
Combined Credit: 47,541,025
DNA@Home: 28,994
SubsetSum@Home: 231,079
Wildlife@Home: 47,280,952
Wildlife@Home Watched: 3,888,714s
Wildlife@Home Events: 628
Climate Tweets: 0
Images Observed: 0

          
Message 2693 - Posted: 19 Apr 2014, 19:36:35 UTC

After ten months of being fairly active here, I finally got some WUs!

How did I miss that the WUs will use more than one core? I have one WU running and it is using up to 65% of my eight core i7 920. When I run two WUs they use almost everything. When three are running I suspect my two GPUs are not being fully fed.
These do not behave like a Yafu@Home multi-core WU, where one uses 100% of the CPU.

Travis or Kyle - do we have a suggested way of running these WUs?

Your WUs do not play nice with other project WUs. They are stealing cycles :)

Profile JumpinJohnny
Avatar
Send message
Joined: 24 Sep 13
Posts: 237
Combined Credit: 10,275,610
DNA@Home: 192,548
SubsetSum@Home: 201,740
Wildlife@Home: 9,881,323
Wildlife@Home Watched: 55,997,833s
Wildlife@Home Events: 15,584
Climate Tweets: 336
Images Observed: 351

              
Message 2694 - Posted: 19 Apr 2014, 20:34:02 UTC - in response to Message 2693.

After ten months of being fairly active here, I finally got some WUs!
...............................
Your WUs do not play nice with other project WUs. They are stealing cycles :)


Ditto: I agree with Gleem. There is something causing problems in the windoz WU's.
On my quad core AMD I noticed that these WU's running on just 2 cores with one other project using a third core and the GPU on a different project as well, (with one core of my CPU open); that I'm getting significant cross usage and "core hogging" that I've never seen before. I can even hear my GPU fan slow down while it's waiting for Wildlife to let loose of the pipeline long enough for the GPU to dump data through the CPU. I've never heard the fan slow down except when I stop the WU's being processed by it.
I do appreciate that I've got my very first Wildlife@Home WU's to crunch, but I am certainly noticing that it's hogging my cpu cores, causing my gpu to stall and actually stopping other normal uses of my computer. Having only one computer I cannot dedicate it full time to running WU's that won't allow it to operate in a reasonable manner. (I don't mind a little lag or some extra heat but can't have BOINC stopping everything.)
I can only hope that this is an issue that can be addressed.
Thanks for your hard work and efforts to allow me to help out with the program.

____________

Profile JumpinJohnny
Avatar
Send message
Joined: 24 Sep 13
Posts: 237
Combined Credit: 10,275,610
DNA@Home: 192,548
SubsetSum@Home: 201,740
Wildlife@Home: 9,881,323
Wildlife@Home Watched: 55,997,833s
Wildlife@Home Events: 15,584
Climate Tweets: 336
Images Observed: 351

              
Message 2695 - Posted: 20 Apr 2014, 19:36:01 UTC - in response to Message 2694.
Last modified: 20 Apr 2014, 19:55:39 UTC

I guess I made that sound a lot more dramatic than it really was.

Actual:
All of the WU's (13) completed and a wingman completed them also, only waiting for a validation from the server.
I was able to run the WU's for windoz on 3 cores of the CPU (AMD), and another Project on the GPU.
There was considerable intermittent lag in using my mouse and opening new web pages was very limited while Wildlife@Home WU's were running.
The GPU WU's were time increased by 28% while Wildlife was using the CPU.

Assumed Summary:
I think that there is probably a very real issue with virtual cores (threads) of the intel CPU's which Gleem spoke of.
I think my issue is probably due to the heavy computations that Wildlife@Home WU's are doing in Windoz.
I was not expecting that and could probably run them just fine if I shut off BOINC from running on the GPU.

Also, my GPU (amd/ati HD4870) is older, (5 years), and I have fairly limited memory (4Gb) installed in my system.
If I spent 4-500 $ on more memory and a newer card, I would still have other bottlenecks.
I understand that these WU's are almost still beta for windoz, so I'm not expecting too much, but do what you can to allow everyone to participate and it will only help Wildlife@Home to advance the goals of the project.

Kyle Goehner
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 17 Feb 13
Posts: 46
Combined Credit: 866,343
DNA@Home: 66,934
SubsetSum@Home: 205,422
Wildlife@Home: 593,987
Wildlife@Home Watched: 44,959s
Wildlife@Home Events: 3
Climate Tweets: 6
Images Observed: 9

        
Message 2707 - Posted: 22 Apr 2014, 15:15:26 UTC - in response to Message 2695.

Currently the WUs take advantage of OpenCV's multicore and OpenCL capabilities. This means some calculations may use the GPU (not heavily) which is why you would see the 28% time increase on the GPU WUs.

I will recompile OpenCV to use a single thread and hopefully this will fix these issues. This may be a couple weeks given my current schedule.

I appreciate your support and feedback.

Thanks,
____________
--
Kyle

Profile Coleslaw
Avatar
Send message
Joined: 22 Jun 12
Posts: 23
Combined Credit: 40,950,784
DNA@Home: 569,863
SubsetSum@Home: 1,698,846
Wildlife@Home: 38,682,075
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 15
Images Observed: 0

        
Message 2720 - Posted: 28 Apr 2014, 20:41:22 UTC - in response to Message 2707.

Currently the WUs take advantage of OpenCV's multicore and OpenCL capabilities. This means some calculations may use the GPU (not heavily) which is why you would see the 28% time increase on the GPU WUs.

I will recompile OpenCV to use a single thread and hopefully this will fix these issues. This may be a couple weeks given my current schedule.

I appreciate your support and feedback.

Thanks,


So are you intending on running these on the GPU's? Or was this an accidental discovery? I'm just curious because I would rather test GPU applications on specific systems whereas testing CPU applications, I'm not as worried about.

Kyle Goehner
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 17 Feb 13
Posts: 46
Combined Credit: 866,343
DNA@Home: 66,934
SubsetSum@Home: 205,422
Wildlife@Home: 593,987
Wildlife@Home Watched: 44,959s
Wildlife@Home Events: 3
Climate Tweets: 6
Images Observed: 9

        
Message 2721 - Posted: 28 Apr 2014, 21:51:17 UTC - in response to Message 2720.

Currently the WUs take advantage of OpenCV's multicore and OpenCL capabilities. This means some calculations may use the GPU (not heavily) which is why you would see the 28% time increase on the GPU WUs.

I will recompile OpenCV to use a single thread and hopefully this will fix these issues. This may be a couple weeks given my current schedule.

I appreciate your support and feedback.

Thanks,


So are you intending on running these on the GPU's? Or was this an accidental discovery? I'm just curious because I would rather test GPU applications on specific systems whereas testing CPU applications, I'm not as worried about.


This was more or less accidental. The program at this point is not optimized for GPU and I don't foresee it being a good BOINC GPU application since it only uses a small portion of the GPU's capabilities. I will more than likely make this a single core program to prevent disruption of other BOINC projects.

At this point I do not know how this will affect performance and runtime.
____________
--
Kyle

Kyle Goehner
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 17 Feb 13
Posts: 46
Combined Credit: 866,343
DNA@Home: 66,934
SubsetSum@Home: 205,422
Wildlife@Home: 593,987
Wildlife@Home Watched: 44,959s
Wildlife@Home Events: 3
Climate Tweets: 6
Images Observed: 9

        
Message 2759 - Posted: 2 May 2014, 4:59:43 UTC - in response to Message 2721.

This issue should be fixed. Please let me know if you notice it hogging cycles or using the GPU.

Thanks!
____________
--
Kyle


Post to thread

Message boards : Number Crunching : How many cores will one WU use?