Stop
24 Dec 2010 20:01:27 UTC
Topic 195534
(moderation:
Hi
I stop wasting time its CPU on this project.
For three days round the clock work, already has earned 512 credits. :)
Patience snapped after sending the last 7 job - no reaction, and "Pending Credit" has not changed.
It turns out that this is all I need is more than you? Fantastic...
Good luck.
Stop
)
I'm not sure I really understand what you are saying but I'll have a go at responding amyway.
You have 4 computers attached to this project so I'm also not sure which particular one is the problem. I saw that your Athlon II X3 440 has had the last 6 tasks aborted and no replacements downloaded so I'm guessing this might be the one you are talking about when you say "Stop".
If you look at the results list for that computer, the last 7 tasks are all dated 24th December for their return. Four are already validated and three are pending ... So I'm really not sure why you think there was a problem?? If you do look at your full three days work, say from 22nd to 24th December, sure there are lots of 'pendings' but look also at all the credits for 22nd December tasks. There is really no problem with this behaviour.
I really don't know what this means but if it's a complaint about not getting credits awarded quickly enough, all you need to do is set your cache size a bit larger (say 3 days total) which would give your wingmen more time to complete and return their tasks in time for your credit to be awarded quickly.
Cheers,
Gary.
RE: . I saw that your
)
It is as a consequence of the stop.
Actually, the whole question of trust.
Perhaps this is some sort of error:
1. hands to "confirm sent"is just some kind of mockery.
2. assignments are given almost instantly, but have to wait almost a month until they build out and find it useful - it's absurd and demotivation.
I'm just guessing incoming jobs and useful to the execution?
Why, then, recognized the work are not counted against for months?
What is the logic and meaning?
Perhaps it is you do not need and can not give points for already?
This is all voluntary work
)
This is all voluntary work here. Nobody is twisting your arm to do it, if you do not like it, well....
Yes there can be times when a job can take a while to get credit for. Lets say you were assigned a job, got it done and reported in 2 days, and I was assigned that same job as your 'wingman'. All of the sudden my computer dies, and goes into the shop. There is a two week timer on the jobs, which means that as far as the server knows, I am still working on that job, it does not know my computer died, how could it? So it will take two weeks before the server says, Hey??? he didn't turn his job in, he's late, Im going to re assign it to someone else. Let's say the job is then assigned to 'john', who happens to have a 10 day cache on his machine. It could now take an extra 10 days for that job to be done and credit given.
For the most part the jobs get done and credits awarded in a fairly timely manner, but there can be circumstances where a job can take a while to get 'counted'. It's part of the process. Patience is a virtue.
Another thing you have to realize is, this isn't a perfect setup. The programs, the codes, all of this, is constantly being worked on to make it better, faster, more powerful. Sometimes there will be speed bumps on the road. We all just have to work through them, give our constructive inputs and help make it right.
Seriously, it's nothing to sweat over.
Merry Christmas.
Aaron
If god meant for us not to BOINC he'd have made our #$%^%^ shorter!!
Ok, I did not understand why
)
Ok, I did not understand why we must push through the job hands and how it relates to probability of failure of Ñomputer .
Merry Christmas.
Vit
Calm down, it's only
)
Calm down, it's only credits...
I have 120 pending results as of 8 AM today, the oldest goes back to the beginning of November. http://einsteinathome.org/workunit/86606939
Enjoy the holiday and relax.
dunx