Message boards :
Number crunching :
new workunit limit
Message board moderation
Previous · 1 · 2 · 3 · 4 · Next
Author | Message |
---|---|
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,525,188 RAC: 0 |
I suspect that all the change really did was reduce the number of work units folks were pulling from the server for about an hour, and that hour is up, so the server is now getting the same sort of constant drone from hungry workstations. It's not gonna work! already I'm getting repeated "No Work Sent" messages and my pc's are backing of to between 1 & 3 hours. Without constant attendance they'll spend most of the time with an empty cache. |
Send message Joined: 4 Oct 08 Posts: 1734 Credit: 64,228,409 RAC: 0 |
Mine are heading that way, but have not reached that point. Most will be out within 30 minutes and the rest will take a little longer. Looks like my parallel projects (Einstein and Malaria) will pull more cores than they expected soon. |
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,525,188 RAC: 0 |
Right, I am now pulling more work down from SETI, POEM and Spinhenge as well. Mine are heading that way, but have not reached that point. Most will be out within 30 minutes and the rest will take a little longer. |
Send message Joined: 22 Mar 08 Posts: 90 Credit: 501,728 RAC: 0 |
Travis, this is hopeless! You need 1 app and spend your time working on it instead of trying to fix all the problems with 10 apps! Its not about the crunchers.... its about the science! While I do like the credit's I'm getting from the opp. app.(credit whore)I joined for the project itself! Get 1 app. working and dont accept work from other apps! A simple "reset project" or "detach/reattach" should take care of it. Put everyone on level ground and get rid of all this drama! If you want to update the app later,... cool EVERYONE updates! Just my 2cents! A clear conscience is usually the sign of a bad memory |
Send message Joined: 5 Dec 07 Posts: 6 Credit: 1,033,816 RAC: 0 |
i guess i will now have to find another project to crunch. i really don't want to crunch seti anymore. all this waiting for work and the new lower 8 wu limits means, based on the past few days, over 1/3rd of the day my fleet will be idle waiting for something to do..esp when the time often goes to 2 hrs and 3 hrs before the server is even contacted again. milkyway has become too hands on lately for me. oh well, it was fun and enjoyable while it lasted... best of luck to everyone......... |
Send message Joined: 6 Mar 08 Posts: 5 Credit: 7,173,397 RAC: 0 |
Hello Travis, 5 WU is nothing. 8 WU per core is better, but still nothing. Can't you increase (400%) the size of the WU? Constant dripping wears away the stone. :) |
Send message Joined: 25 Nov 07 Posts: 11 Credit: 40,758,862 RAC: 0 |
this project has now become a waste of my time. 80% of your problems would go away just by increasing the size of the wu's. this would be a good Idea when you switch to the new app. But for now, it has been placed as a backup project with my computers. |
Send message Joined: 18 Nov 07 Posts: 280 Credit: 2,442,757 RAC: 0 |
this project has now become a waste of my time. Oh come on, at least read the damn thread. Travis has already said that increasing the size of WUs is on the agenda, but that doing this isn't as easy as we may think. |
Send message Joined: 25 Nov 07 Posts: 11 Credit: 40,758,862 RAC: 0 |
this project has now become a waste of my time. 1% resource share seems to be doing well with the project at the present time. the only real computer now running the project is My atom 230 system. My dual xeon and core-i7 systems just go through the project too fast to even worry about running the project on at the present time. |
Send message Joined: 13 Jan 08 Posts: 19 Credit: 820,482 RAC: 0 |
30/11/2008 10:19:29|Milkyway@home|Message from server: No work sent 30/11/2008 10:19:29|Milkyway@home|Message from server: (reached per-CPU limit of 8 tasks) 30/11/2008 10:20:30|Milkyway@home|Sending scheduler request: To fetch work. Requesting 65098 seconds of work, reporting 0 completed tasks Even after running alnight still have a full download of 32 on both quads and 16 on laptop Increase from five to eight nice one. How about another approach claimed credits as against granted credits seems to work alright on other projects. Michael |
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,525,188 RAC: 0 |
One thing to consider here, given the fragility of the servers, the workload presented by the use of the optimized client, and the 'interesting' approach for awarding credits, it seems to make some sense to NOT use the optimized client. Since the current award scheme seems to be based on cpu time spent and not work done, there is no 'credit penalty' for running the vastly less efficient regular client. The other benefit is that with the much longer running time of the regular client, and the miniscule cache, users don't spend an inordinate amount of time trying to pry a 5 minute work unit from the gasping server, rather, each work unit runs 5 hours. The two downsides to this are, one produces less science (but perhaps the optimized client produces too much work for the project to handle anyway), and the extra time processing on MilkyWay (for which you get an ample credit award) is not spent on other projects. I'd not suggest this at all if the credit scheme were work based instead of CPU time based, nor would I suggest this at all if adequate work was readily available and rational queues of say 10 to 24 hours were available. But there it is. I'm seriously considering dumping the optimized client out in favor of the very inefficient 'regular' client -- it will mean I have more time to spend on other things. |
Send message Joined: 7 Jun 08 Posts: 464 Credit: 56,639,936 RAC: 0 |
LOL... I was thinking along the same lines, but to even suggest not using the opti borders on heresy in some circles. :-D Even if that means it drives the project to near meltdown. ;-) As far as scoring goes, agreed. If the basis was set to something closer to the current 'nominal', there would probably a lot less CW'ing going on. ;-) Alinator |
Send message Joined: 22 Nov 07 Posts: 285 Credit: 1,076,786,368 RAC: 0 |
5 was too low, 8 is too low - Travis, your network, and servers were having a hard time keeping up with the demand at 20? If you feel you need to lower it, do so, but make it reasonable - 10-15 would be a much better figure. My hosts are constantly asking for more work, and if this is causing my network trouble, I am sure it is causing your systems to cry out in pain. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
This should be a non-issue now that we're moving over to the new application. WUs for that should be quite a bit longer. |
Send message Joined: 4 Oct 08 Posts: 1734 Credit: 64,228,409 RAC: 0 |
I presume the best way to install the new client is to detachand reattach, as it is now the stock client? I have downloaded the 1.5 Mb windows Zip file and unzipped it. But there is no install instructions I can see. How simple is it? Is it just copying it in to the project file in the BOINC folder? |
Send message Joined: 12 Nov 07 Posts: 2425 Credit: 524,164 RAC: 0 |
I presume the best way to install the new client is to detachand reattach, as it is now the stock client? Isn't that just the app so it can be optimized? The new app should auto. download right? Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
I presume the best way to install the new client is to detachand reattach, as it is now the stock client? Yeah, the new app should automatically download. Update: I edited the news post so people don't get confused and think they need to compile it themselves :) |
Send message Joined: 21 Nov 08 Posts: 90 Credit: 2,601 RAC: 0 |
I presume the best way to install the new client is to detachand reattach, as it is now the stock client? Make sure you dont have an app_info file in the milkyway folder, then the new program will arrive as soon as its released. |
Send message Joined: 4 Oct 08 Posts: 1734 Credit: 64,228,409 RAC: 0 |
Detached my first quad and reattached. The system automatically downloaded the new client and the 8 WUs-per-core limit and got on crunching. The WUs are labled as - Milkyway@Home optimised 0.04. I assume 0.04 WUs go with the 0.5 client? These WUs are definitely slower than the Milksop client, which was being crunching on an average of 200 - 205 seconds. Looking at the first 4 crunched on the rig I type from, the average time is 505 - 514 seconds. That means they are about 2.5 times as long. |
Send message Joined: 7 Jun 08 Posts: 464 Credit: 56,639,936 RAC: 0 |
Detached my first quad and reattached. The system automatically downloaded the new client and the 8 WUs-per-core limit and got on crunching. Hmmm... Well one thing to keep in mind here, is that the detach and or reset will dump the app_info file (and opti) from the project directory. What isn't clear so far is; Are the Astronomy searches (gs series) completed now? If not, then you need to build the custom app_info I mentioned in another thread or you are going to have a TDCF mess if and when the CC picks up an Astronomy task and runs it with the stock version. Alinator |
©2024 Astroinformatics Group