log in |
Message boards : Number crunching : Long 2 are a joke
1 · 2 · 3 · Next
Author | Message |
---|---|
http://srbase.my-firewall.org/sr5/result.php?resultid=359194127 | |
ID: 4755 · Rating: 0 · rate:
![]() ![]() ![]() | |
http://srbase.my-firewall.org/sr5/result.php?resultid=359194127 It looks like that your CPU is running on HT. The app is highly optimised. | |
ID: 4756 · Rating: 0 · rate:
![]() ![]() ![]() | |
Yes I have an iMac (late 2009), HT is not an option here (you can't switch it off). | |
ID: 4757 · Rating: 0 · rate:
![]() ![]() ![]() | |
just use mt, it helps to get them back within the deadline | |
ID: 4758 · Rating: 0 · rate:
![]() ![]() ![]() | |
I don't understand "just use mt" ? | |
ID: 4759 · Rating: 0 · rate:
![]() ![]() ![]() | |
use app_config.xml to say boinc, that llr should use multiple cores for one task | |
ID: 4760 · Rating: 0 · rate:
![]() ![]() ![]() | |
It is in the FAQ thread here http://srbase.my-firewall.org/sr5/forum_thread.php?id=6 | |
ID: 4761 · Rating: 0 · rate:
![]() ![]() ![]() | |
Interesting, I didn't know about the multi-threading on SRBase, I knew about it on Primegrid and have implemented it there. | |
ID: 4762 · Rating: 0 · rate:
![]() ![]() ![]() | |
Regarding the mt : now I remember that, I even think I had implemented it long time ago. But obviously it got lost in my boinc setup somehow... | |
ID: 4763 · Rating: 0 · rate:
![]() ![]() ![]() | |
I did the app_config thing, I'll see what happens the next time I get some SRBase in my machine. | |
ID: 4764 · Rating: 0 · rate:
![]() ![]() ![]() | |
Yes, well, after doing the app_config.xml, I now get nothing but errors. | |
ID: 4765 · Rating: 0 · rate:
![]() ![]() ![]() | |
Mine work using <cmdline>-t4</cmdline> | |
ID: 4766 · Rating: 0 · rate:
![]() ![]() ![]() | |
Thanks PDW, | |
ID: 4767 · Rating: 0 · rate:
![]() ![]() ![]() | |
I got lucky with that long running task of mine, it ran for over 972,000 seconds (270 hours or 11.25 Days), and I managed to get it back first, so got the points. | |
ID: 4768 · Rating: 0 · rate:
![]() ![]() ![]() | |
I got lucky with that long running task of mine, it ran for over 972,000 seconds (270 hours or 11.25 Days), and I managed to get it back first, so got the points. As long as the second result not came back all other WUs are still valid. | |
ID: 4770 · Rating: 0 · rate:
![]() ![]() ![]() | |
Thanks PDW, I have downloaded and am now running a Long2 work unit. After 8 hours it shows over 14% done, which is a lot quicker than before. @ PDW, I am showing all 4 threads on a 4 core computer being recorded at WUProp, 8 hours done and showing 31.6 hours, which seem right to me. I do have an extra line in my app_config.xml file that may be what is different to what you have. I have <cmdline>-t4</cmdline> <avg_ncpus>4</avg_ncpus> Not sure if this might be how I am getting all threads picked up or not. Anyway all seems to be working again, Thanks Conan | |
ID: 4773 · Rating: 0 · rate:
![]() ![]() ![]() | |
No, you don't have to integrate an extra line with "avg_ncpus" because you don't want to separate between threads and cpu cores. You should use the "<project_max_concurrent>1</project_max_concurrent>" command, which tells the project to only use one single wu overall. At least to me this is usefull in a time where most of the wus are long type. So the app_config in the FAQ becomes useless at the moment where the project uses different apps (and this happens very often), because in this way every of the 12 possible apps is allowed to use the number of cores you set in the config file. The result is that you still have 4 threads on a 4 core cpu with the little difference that now the OS switches the cores between the tasks, so you can have a long task with 70% cpu, a long3 task with 20% and 2 short tasks with 5% each, instead of 4x 25%. But in the end, no time is won, because you want to use 100% of you cpu to only one single long task. So a usefull app_config (with a proper formatting, unlike in the FAQ) where all cpu cores (4 in this case) concentrate to only one wu should look like this: <app_config> <app> <name>srbase</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase2</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase3</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase4</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase5</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase6</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase7</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase8</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase9</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase10</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase11</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <app> <name>srbase12</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase</app_name> <cmdline>-t4</cmdline> </app_version> <project_max_concurrent>1</project_max_concurrent> <report_results_immediately/> </app_config> | |
ID: 4815 · Rating: 0 · rate:
![]() ![]() ![]() | |
You have all your app_versions as "srbase" and not "srbase2" "srbase12" etc... | |
ID: 4850 · Rating: 0 · rate:
![]() ![]() ![]() | |
Just cancelled bunch of "long" wu's (I gave it a chance; some wu's were running for 4+ days and at 95%). Short wu's fine, but i'm not going to waste anymore resources to this "long" sh*t! | |
ID: 4851 · Rating: 0 · rate:
![]() ![]() ![]() | |
Here is what I've wound up using on my 4790K, and it seems to work quite well - I DID have to add the "ncpus" in there so BOINC would report them as using 3 CPUs. I also note that usage never gets over about 130% (100% = 1 core) even though 3 are specified. Other apps run up to 287%. However, it works, I'm not going to mess with it. | |
ID: 4854 · Rating: 0 · rate:
![]() ![]() ![]() | |
Message boards :
Number crunching :
Long 2 are a joke