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: 55
|
![]() |
Author |
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12561 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Pete Broad & Nanoprobe
It is possible to restrict the number of any projects running using app_config however I don't know the specific code for the current mcm beta. It might be beta27. I know all the other project codes. Mike |
||
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 837 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Mike is right: It's beta27 according to client_state.xml
----------------------------------------
[Edit 1 times, last edit by hchc at Jul 23, 2020 12:15:24 PM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7777 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I have received 14 of the beta's this round with all of them on Linux. I have yet to get one on my one Windows machine so I can't compare yet. But the Linux versions are all running consistently between 3.25 and 3.7 hours on Linux machines using Xeon 5645, 5650 and 5670 cpu's. All are running with OPN units and hyperthreading. No apparent problems.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
RogueHAM
Cruncher United States Joined: May 26, 2020 Post Count: 3 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() |
2 Ran yesterday on PI4 4GB running Raspbian without issue , 4.34 hours. Posting since people asked last time if any ARMS were sent out
---------------------------------------- |
||
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1311 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
On my Ryzen 3900 X I had several tasks they ran between 0.98 and 1.32 hours Windows 10 professional
----------------------------------------![]() |
||
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12561 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Thanks, hchc.
----------------------------------------If you want to restrict the number of threads running any project without restricting the cache. you need to put this bit of coding into a file called app_config.xml <app_config> <app> <name>arp1</name> <max_concurrent>2</max_concurrent> </app> <app> <name>mcm1</name> <max_concurrent>2</max_concurrent> </app> <app> <name>fahb</name> <max_concurrent>8</max_concurrent> </app> <app> <name>scc1</name> <max_concurrent>7</max_concurrent> </app> <app> <name>opn1</name> <max_concurrent>8</max_concurrent> </app> <app> <name>hst1</name> <max_concurrent>8</max_concurrent> </app> <app> <name>beta27</name> <max_concurrent>8</max_concurrent> </app> <app> <name>mip1</name> <max_concurrent>1</max_concurrent> </app> </app_config> The number in the middle of the concurrent line is the number that you wish the project to be restricted to. Each project has 4 lines and you can delete those that you don't wish to restrict or that you don't actually download. The file path for where to put that file is: C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org You activate this by clicking on 'Options' and then 'Read config files' Mike [Edit 3 times, last edit by Mike.Gibson at Jul 24, 2020 11:41:14 AM] |
||
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2217 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I was getting quite enthusiastic about the apparent performance improvement I was seeing in the second set of Beta test tasks here, until I realized that every single task I received in the second set uses VMethod=LOO whilst every one I checked in the first set used VMethod=NFCV. It has been my experience that pre-Beta MCM1 NFCV tasks for SARC1 take about 125% longer than LOO tasks on all my Intel machines, and about 25% longer on my Ryzen 3700. The differences I'm seeing between the first and second sets of Beta runs here reflect much the same differences (though, if anything, the first set (NFCV) were slightly worse on the Intel machines. [...] are we going to switch all processing to VMethod=LOO??? ![]() [Edit 1 times, last edit by adriverhoef at Jul 24, 2020 12:48:21 PM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7777 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Just one little glitch here. I have several machines running Linux, but on one of them which has been running exclusively OPN, one of the downloads for the beta was 103 megabytes and unfortunately the download hung. The only reason I checked that machine was it had not reported the betas as being finished, still in progress after a couple of days. I managed to get the hung download restarted by suspending network activity and re-activating it several times. The hung download was also preventing any downloads from OPN, so when the beta download became active and started working again, I also resumed getting OPN downloads. Since I only run with 1 day cache, I had run out of OPN work units. The upload of completed OPN units was unaffected. I have not experienced this behavior on this machine prior to this instance. I have 4 machines on that range extender and there was no problem with the other machines. It could just be a fluke for that machine.
----------------------------------------So far the betas are running normally and should finish close to the deadline. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Pete Broad
Senior Cruncher Wales Joined: Jan 3, 2007 Post Count: 169 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Thanks, hchc. If you want to restrict the number of threads running any project without restricting the cache. you need to put this bit of coding into a file called app_config.xml <app_config> <app> <name>arp1</name> <max_concurrent>2</max_concurrent> </app> <app> <name>mcm1</name> <max_concurrent>2</max_concurrent> </app> <app> <name>fahb</name> <max_concurrent>8</max_concurrent> </app> <app> <name>scc1</name> <max_concurrent>7</max_concurrent> </app> <app> <name>opn1</name> <max_concurrent>8</max_concurrent> </app> <app> <name>hst1</name> <max_concurrent>8</max_concurrent> </app> <app> <name>beta27</name> <max_concurrent>8</max_concurrent> </app> <app> <name>mip1</name> <max_concurrent>1</max_concurrent> </app> </app_config> The number in the middle of the concurrent line is the number that you wish the project to be restricted to. Each project has 4 lines and you can delete those that you don't wish to restrict or that you don't actually download. The file path for where to put that file is: C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org You activate this by clicking on 'Options' and then 'Read config files' Mike Thanks, I'll try that. Pete ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Mike is right: It's beta27 according to client_state.xml Yet my client responds by using beta17 in app_config and one of the project files is named wcgrid_beta17_map_7.57_windows_x86_64. Beta27 was the ARP1 beta. Historically the BetaNN marker has always stayed with a project for it's lifetime. This ensures that in 10 years time you'd still know it was about X and not Y. [Edit 1 times, last edit by Former Member at Jul 26, 2020 8:35:31 AM] |
||
|
|
![]() |