They're on the same team too...
http://asteroidsathome.net/boinc/team_members.php?teamid=2022&offset=0&sort_by=expavg_credit

BTW, another thought has crept into my mind. Some of the lads get up to all sorts of shenanigans when there is a challenge going on. If you look at the OS recorded for each of those hosts it says they're Linux virtual hosts. I am beginning to wonder if some joker didn't fake 32 cores on a 4 core virtual machine and then clone that original into 130 bogus hosts. It's an entirely doable scenario and I know because I've done similar myself. Now each of those clones has downloaded a few thousand tasks for a total of over 100,000 but they're all running on just a single 4 core i5 CPU. Hmmmmmm?

Brilliant deduction! First of all that team wasn't in the challenge. Secondly I'm impressed that "fake" machines could throw up 61M credits in a week. I need to check into how that's done.


http://stats.free-dc.org/stats.php?page=userbycpid&cpid=68583442208b71aea7c8eed7bc0f4784

Hmmm. That blows a pretty big hole in my theory. It's too late now but I did notice his huge RAC a few hours prior to posting my quack theory but forgot all about it. For my penance I will PM Jamie and straighten him out. I hope he doesn't punch me in the eye. With that RAC he's starting to sound like a pretty tough hombre.

@Andrew:

LOL! I did clone a few virtual hosts once but not for the purpose of hoarding tasks. And as Bryan pointed out my theory doesn't hold a lot of water anyway. I hope we can all get along too and I apologize for egging you on.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

The problem with HUGE users is that they will just go elsewhere with their resources if they can't get what they want here. There are ALSO plenty of projects that do NOT throttle the workunit load. I am guessing most projects would LOVE to have some super user come in with this guys resources and start crunching for them. This ONE guy is like adding 100 of us normal folks.

I think Gerard meant 5 cached tasks per core not 5 per core per day. BOINC server has a setting for it.

With a max of 5 in the cache at any given time any user with 24/7 connectivity would have all the tasks he can crunch. Only hosts that have limited connectivity (eg. traveling laptops) would be affected.

And we don't yet know if the person/persons involved have 24/7 connectivity. My old work cut the network at night to prevent unauthorized access by certain workstations. YES of course the net still worked on some but most had their internet cutoff by software on the Server side. They also had software that physically shut them down at 9pm at night too. They got a grant from the local power company to do that instead of the power company building a new substation.

No problem. The server is back up, so I'll give it another try..... POGS is working really well....

Approximately 1/3 of all of my validation tasks were timed out by my wing men. The vast majority of them being Mr. Kinney and Mr. Broiles. No biggie.....

And we don't yet know if the person/persons involved have 24/7 connectivity.

I figure those 130 machines must be servers therefore assume 24/7 connectivity. If he has permission to install BOINC on all of them then I doubt his account's connectivity is restricted.

Even a restriction of 20 cached tasks per core would be a big help in solving the problem. If one assumes ~1 hour per task then 20 tasks per core should be enough to last from 1 connected window to another. It wouldn't be perfect for everybody but the pros definitely outweigh the cons. Remember back to several months ago when Kyong made a mistake on the task duration estimate and everybody got 10 times as many tasks as they should have. The kind of restriction we're talking about would have helped a lot in that situation too.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

And we don't yet know if the person/persons involved have 24/7 connectivity.

http://www.planetaryresources.com/

I'm pretty sure they are online 24/7...

I figure those 130 machines must be servers therefore assume 24/7 connectivity.

You're kidding me ?!? Of course those machines are servers !

If he has permission to install BOINC on all of them then I doubt his account's connectivity is restricted.

I'm guessing it's in their best interest to run asteroids@home given the link i posted above... Guess what that company is interested in ...

Even a restriction of 20 cached tasks per core would be a big help in solving the problem. If one assumes ~1 hour per task then 20 tasks per core should be enough to last from 1 connected window to another. It wouldn't be perfect for everybody but the pros definitely outweigh the cons. Remember back to several months ago when Kyong made a mistake on the task duration estimate and everybody got 10 times as many tasks as they should have. The kind of restriction we're talking about would have helped a lot in that situation too.

Bla bla bla... just limit the "in progress WUs" per core to let's say 15... that'll solve the "problem" for those that can't wait... Instant credit would't that be cool ?!?... Not going to happen here... So why don't you all chill till you get your credit... ?!?

---

Join BOINC United now!

If he has permission to install BOINC on all of them then I doubt his account's connectivity is restricted.

I'm guessing it's in their best interest to run asteroids@home given the link i posted above... Guess what that company is interested in ...

They want pizza delivered hot in 30 minutes or it's free??

Instant credit would't that be cool ?!?

If'n I had my druthers there'd be no credits at all, Unca Jed.

So why don't you all chill till you get your credit... ?!?

I'm here to do science and troll the newbies, credits just make me puke. I don't even like the badges. Look like loaves of mouldy bread to me.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux