I agree with P4 getting more credit for the WUs they run. That's what's fair about. A CPU second is a CPU second. The P4 runs 1 WU and the Quad will run 4 WUs. Same Credits for 8 Hours of work.

That's like saying 2 Sprinters should get the same Gold Medal even though 1 of the Sprinters who was older & slower only ran 1 Lap while the other younger & faster Sprinter ran 4 Laps of a Race.

In your View since they both spent the same amount of time on the Race Track then they both should receive the same Reward even though 1 ran 1 Lap & the other 4 Laps ... ???

I'm not sure what happen in Nov 2006 besides one of my hosts crashed and then the problem bagan. All my old projects had there CPIDs stolen away in this transition. :D What I can't figure is how can a host have different CPIDs (4 in most of them) and control/change the Project CPIDs when they connect. I thought the Projects Servers controled the hosts. The one good thing is I got down from 10 CPIDs to 4. I even detached from BAM to see if CPID Problem would clear up but it didn't

When BAM retires a project they detach all the hosts from the project and it keeps detaching them for an eternity. An example is ABC@Home Beta. It only has work as needed (Nov 2007 was last WU I finished) & it wasn't reachable for a while so I guess that is why they retired it. I attach to it ever once in a while to see if it up and as soon as my host syncs BAM it detached. If It does give out any work, I'll have to Detach from BAM to run it.

I had the same Problem for about 2 Years myself, my Stats would jump up & down at the Stat's Sites



Hmmm...

Now that is interesting. I seem to remember loosing a couple of host CPID's on BOINCStats around then, but everything resync'ed on the same Account CPID.

The only side effect was a couple of hosts lost their graphical data for everything from before the event.

Let me check my logs and get back to you on this.

Alinator

I tried everything to solve the problem. Including begging the Dev (which is a low priorty issue). I would like to see if they could straighten out the problem, but I think I going to detach 15 hosts from all the projects, delete/clear out all BOINC. Then go into one node and change all the CPID to my main one (or suspose to be my main one) then run it until I get all the projects to Sync with my host. Then put the others back online again.

I had the same problem for about 2 Years myself, my Stats would jump up & down at the Stat's Sites because the Projects I ran would fail to keep the same CPID across them. I tried everything from editing the .xml files to trying some suggestions JMV gave me which didn't work either.

What I finally discovered was that 1 Project was the key to keeping the same CPID at all the other Projects, that Project for me was Pirates@Home. As soon as I attached Pirates@Home to all my Computers the CPID straightened itself out across the Projects and to this day I don't need to have Pirates Attached anymore but do keep it attached to 1 Box just for old times sake ... :)

So maybe thats what you need to do, find the Key Project, it's more than likely 1 of the first Projects you ever ran as Pirates was for me, it's something to think about and look for anyway ... Good Luck

@ KAMCOBILL:

Hmmm...

I looked over my logs and the event I had was about the time your problem started.

However, I don't use BAM or any other account manager, and my logbook noted that the most likely cause for mine was that Willy was experiencing some growth problems at the time and having some DB difficulties as a result.

So since I have no experience trying to get a CPID to sync up in your situation, I can't really say whether your next attempt strategy is good, bad, or futile! :-(

All I can say is it sounds like a plan, good luck, and I hope it works for you this time! ;-)

Alinator

I'm not sure what happen in Nov 2006 besides one of my hosts crashed and then the problem bagan. All my old projects had there CPIDs stolen away in this transition. :D What I can't figure is how can a host have different CPIDs (4 in most of them) and control/change the Project CPIDs when they connect. I thought the Projects Servers controled the hosts. The one good thing is I got down from 10 CPIDs to 4. I even detached from BAM to see if CPID Problem would clear up but it didn't

When BAM retires a project they detach all the hosts from the project and it keeps detaching them for an eternity. An example is ABC@Home Beta. It only has work as needed (Nov 2007 was last WU I finished) & it wasn't reachable for a while so I guess that is why they retired it. I attach to it ever once in a while to see if it up and as soon as my host syncs BAM it detached. If It does give out any work, I'll have to Detach from BAM to run it.

Hmmm...

Now that is interesting. I seem to remember loosing a couple of host CPID's on BOINCStats around then, but everything resync'ed on the same Account CPID.

The only side effect was a couple of hosts lost their graphical data for everything from before the event.

Let me check my logs and get back to you on this.

Alinator

OK By Gosh I think I got it. Give 1 credit per CPU second for all projects.

So my 200 MHz is worth the same a a Core 2 3GHZ? This does not seem very bright.

My Pentium III says "Goodbye" to Milkyway.
The new workunit-length is killing my machine!!!
When Workunit-length is shortened, mayby he ´ll be back ...

I'm not sure which projects it was (I thought it was this one but maybe not I'd have to check posts) in early stages the WUs were aborted with because maximum CPU time exceeded. Anyway, I thought it was the projects that was aborting because I don't see a setting In BOINC Manager or BAM to set a CPU Max Time and they weren't running too long before being aborted.

Actually, My PIIs don't do too bad. They are definately better than the Cyrus 100 & AMD 100 I retired. Never tried an AMD 25 though :D. I do have more MW WUs left in the PII that aren't going to make it by deadline because when I got them Time to finish was like 20+ minutes but now it's 68+ hours.

Hehe. My Pen D 3.0Ghz had a hard time meeting the deadlines but they did. It went from 6 to 9 mins to 9+ hours on them. Hopefully, they are ready to crunch with ease again.

The max run time is set by the project administrators. I believe that Orbit recently had this problem.

Also, I think there is something funny with the RS project's server code. If RS was the oldest project, it still won't sinc up properly sometimes. Add to that, RS being currently down...

Hmmm...

Well, that might be due to RS having the secondary objective of porting BOINC to php.

OTOH, I haven't had any trouble with my CPID sync'ing up because of RS (or any other project for that matter). Although it did seem to take longer than usual after joining. IIRC, it took about a week or ten days to sync to my 'permanent' CPID instead of the usual couple of days after the first task completed and went through a stat xml cycle.

I hadn't thought about what the effect would be if RS was the oldest project or what would happen if the oldest project wasn't available though.

Of course, I don't have that many hosts or run anywhere near the number of projects available today. The one thing which is true is SAH is my oldest project and all my hosts are attached to it. The other thing which is true is there are still some basic operational areas in BOINC which are kind of shaky and can definitely rear their ugly head given the right set of conditions (like the primary topic in this thread, for example). ;-)

@ KAMCOBILL: Based on your last post (about the CPID problem anyway), this would seem to indicate a BAM problem rather than BOINC per se. I never ran any of the 'retired' projects. However, I used to run Predictor but it remains linked to my CPID even though I haven't crunched a task for them in ages, and have gone months without even doing an update on any of the hosts which are still attached to it.

Alinator

Credits Calculations vs. Credit (CPID) Problems? I wish as much effort would go into getting the Credits straight as in the Granting of Credits/cross project parity.

My Credits http://boincstats.com/stats/boinc_user_graph.php?pr=bo&id=b65b36154e3a49f636a3148d4e0b3c83 have been seesawing back and forth since Nov 06. Actually, I'm not into this for Credits, but it would be nice to look at once in a while to see how my efforts compared to others. So as it stands for me, it doesn't matter if I get 1 or 1000 Credits/Hour because it doesn't show in any stats that use CPIDs for their stats.

Since I only have 2 cents I don't want to spend it all here. :D Patience is a Virtue.

You have two different CPIDs. The solution: Attach one machine to ALL projects you have done work for. Cycle through the projects with update giving at least three complete successful cycles.

Second solution. The BOINC client and server have (very recently, not released yet) been modified to incorporate an extra time stamp on the CPID. This will eventually fix the problem automatically.

Sorry for all the confusion, I did make a post about the increased time for WUs when I did it, but I realize that "at the same time" wasn't enough time for some of you guys to realize what was going on. Thanks to those that pointed the others in the right direction.

The answer to the big question is YES, the deadlines will be changed. The only reason it hasn't been done yet is that I do not know how, and Travis is out of town until today or tomorrow. However, it will be fixed ASAP.

As for all the credit issues, my personal belief is that there should be a standard BOINC implementation that gives 1 credit per minute crunched. Simple sweet and no worrying by the project admins if there is too much or too little. But, that's just my opinion. However, I do understand why it's not universal and, so we deal with it.

Hello To all fellow crunchers here at milkyway@home

I noticed a while ago in the messages tab:

19/11/2007 15:46:11|Milkyway@home|Message from server: No work sent
19/11/2007 15:46:11|Milkyway@home|Message from server: (reached per-host limit of 8 tasks)

Is this right?
Are there new limits being set?

As previously the quota was set in the thousands per host.

Kind Regards,

John Gray :0)

At the moment there is a limit of 2000 units per core per day. But the project is set to limit the number of units per host to 8 at one time. As these are reported back you receive more. The only people that might have a major problem with this would be those that don't have a continuous connection and run this project exclusively.