Some Work Units Really Taking Way Too Long

North95
North95
Joined: 11 Feb 05
Posts: 37
Credit: 24520
RAC: 0
Topic 188329

I have a good example of a work unit that tied up one of my processors for way too long. I complained before, when it wasn't complete, but now you can see it on my results page. Result ID 1292702, Work Unit ID 371572, took a whopping 105,665 seconds. It claimed credit of 149.36 and 87.31 was granted. Other computers took 18,602 sec, 20,783 sec, 46,446 sec and 82,329 sec.

Usually my computer is somewhere in the middle in terms of speed. For example, my latest unit, Result ID 1449411, Work Unit ID 407717 took my computer 29,649 sec. The other computers took 19,348, 53,065 and 98,360 sec. I claimed 41.91 and was granted 89.47.

In fact, of the fourteen units on my list now, I was granted more credit than claimed on all except two.

I realize there are different computers at different speeds working of each of the units.

Its just weird that this unit took so long. All the rest took 40,000 to 50,000 seconds, but this one took 105,000 seconds. Thats more than a factor of two difference.

Anyone know an easy way to abort a unit?

I started missing the 7 day deadline while this unit was running and lost credit for one unit. I've been decreasing my cache down now to .5 days, and decreased my share of Seti to 10 a week ago. Einstein share is 100.

BTW, this is a dual processor Mac G4 1.25GHz running 24/7. And I make sure that nothing else is running when I'm not here.

Any ideas?

North

"Try not. Do. Or do not. There is no try." - Yoda

[img]http://www.boincstats.com/stats/banner.php? cpid=418c9a98efef17b0f7b6237ff6826201[/img]

Jim Harris
Jim Harris
Joined: 22 Jan 05
Posts: 8
Credit: 30140
RAC: 0

Some Work Units Really Taking Way Too Long


> Any ideas?
>
> North

Hi, A quick answer for you is this workunit plus several other workunits of yours were executing debug code and increasing the cpu times.

http://einsteinathome.org/task/1292702

-core_client_version>4.19-/core_client_version>
-stderr_txt>
APP DEBUG: Application caught signal 2
Resuming computation at 4170/427580/427580
APP DEBUG: Application caught signal 2
Resuming computation at 5151/509298/509298
APP DEBUG: Application caught signal 2
detected finished Fstat file - skipping Fstat run 1
APP DEBUG: Application caught signal 2
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 396/44909/44909
APP DEBUG: Application caught signal 2
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 23281/1468668/1468668

-/stderr_txt>

Can't tell you why but the admins might?

North95
North95
Joined: 11 Feb 05
Posts: 37
Credit: 24520
RAC: 0

> > Hi, A quick answer for

Message 7361 in response to message 7360


>
> Hi, A quick answer for you is this workunit plus several other workunits of
> yours were executing debug code and increasing the cpu times.
>

Thanks. That's interesting. I didn't notice that. I wonder what that means.

North

[img]http://www.boincstats.com/stats/banner.php? cpid=418c9a98efef17b0f7b6237ff6826201[/img]

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.