Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 73
|
![]() |
Author |
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1311 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I will pass on the details about having cpu/os information in the stderr. I believe however it will be easier for just having it in the result page instead. Since that data is already collected by BOINC on a host level. Thanks, -Uplinger Uplinger I am sure you have a valid reason for not including the information. I feel it will allow people like myself who wonders why the other person completed the task a lot faster than my host, information on the OS and CPU type would answer all those questions. Would it be possible to include it another way? This is just my point of view on how I think this information would be helpful. Unfortunately I did not get any tasks this round. I am hopeful I will get some in following rounds All the best for people who are in the hunt to greater there beta badge ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi.
----------------------------------------Are we checking to see if the graphics are working on Ubuntu rigs this time to make sure they are. ![]() ![]() [Edit 1 times, last edit by Former Member at Jul 30, 2014 8:01:15 AM] |
||
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3297 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Graphics didn't work on Linux Mint but MCM graphics also don't work. A windows opens and almost instantly closes.
----------------------------------------![]() - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Edit: P.S. - Any sharable info on projected system requirements for the new project other than SSE2? The initial memory requirements are going to be rather low. I would say less than 50MB. The bandwidth usage for this project may be large for runtime of a work unit. The work units we tested in this beta were small. Remember this is just initial data and can change when we get closer to release. Thanks, -Uplinger |
||
|
ThreadRipper
Veteran Cruncher Sweden Joined: Apr 26, 2007 Post Count: 1324 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I got five on my PC yesterday, and now they are finally close to start. I would like a way to be able to force start (or set priority on) a WU. Since I got these beta WUs yesterday I wanted to mark them and clock somewhere on a button saying that the selected WUs in the cache will be prioritized as soon as there is a free core (becaus another WU currently running has completed).
----------------------------------------Anyway, will be interesting to see how these fare on an OC'd 3930K @ 4.3GHz and the data directory on a RAMDisk. ![]() Join The International Team: https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=CK9RP1BKX1 AMD TR2990WX @ PBO, 64GB Quad 3200MHz 14-17-17-17-1T, RX6900XT @ Stock AMD 3800X @ PBO AMD 2700X @ 4GHz |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I find that if you suspend the other wu's that have not yet started on your rig then each time a wu completes a beta will take its place. unfortunately you do need to be watching quite closely for the last beta to start in order not to have idle cores. Using Boinctasks makes this somewhat easier.
----------------------------------------![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I find that if you suspend the other wu's that have not yet started on your rig then each time a wu completes a beta will take its place. unfortunately you do need to be watching quite closely for the last beta to start in order not to have idle cores. Using Boinctasks makes this somewhat easier. That is what I do if I want a particular WU to be next ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just suspend all other tasks, including running ones, perhaps staggering the timing of the last few tasks so that not all downloaded Betas start all at once. Once the Betas are running, I then resume the suspended tasks. At least with BOINC 7.2.47, priority is then given to running tasks, so I find that the Betas finish before any waiting task actually runs again. This way, I don't need to watch for any idle cores. The LAIM option (Leave Applications In Memory) is best on for this to be efficient.
|
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4892 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I find that if you suspend the other wu's that have not yet started on your rig then each time a wu completes a beta will take its place. unfortunately you do need to be watching quite closely for the last beta to start in order not to have idle cores. Using Boinctasks makes this somewhat easier. Or you can suspend all non-Beta WUs thereby letting the Betas start, and then immediately resume all suspended WUs. The Betas will continue running and no WUs will remain suspended. Your suspended WUs will revert back to the last checkpoint, but this is only a big deal if you are running CEP2. [Edit 1 times, last edit by deltavee at Jul 30, 2014 4:58:09 PM] |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I test by first turning LAIM off therefore I prefer to let the pre running other wu's complete. (especially CEP2) When there are greater numbers of betas I try both LAIM settings.
----------------------------------------![]() |
||
|
|
![]() |