I don' understand why I have so many pendings. Can anyone tell me why I keep getting them? I update everyday, once a day when I get home, but the pendings keep staking up. Sometimes I get credit after a task is complete, sometimes all i see is "pending." no compute errors or anything. the taks were successful. can anyone help?
-jrt

I don' understand why I have so many pendings. Can anyone tell me why I keep getting them? I update everyday, once a day when I get home, but the pendings keep staking up. Sometimes I get credit after a task is complete, sometimes all i see is "pending." no compute errors or anything. the taks were successful. can anyone help?
-jrt

The pendings have almost nothing to do with you. They just mean you are waiting to get credit for quorum partners to return their results on the same work unit.

When you get instant credit, your quorum partner returned before you, which means that he saw pending until you returned.

My advice is not to worry about it. There is, however, one thing you can do which will make it less likely. You can use the "maintain enough work for an additional n.nn days" parameter under general preferences to get your results longer before you process them.

Doing this, will, however, keep your quorum partners waiting longer.

---

I don' understand why I have so many pendings. Can anyone tell me why I keep getting them? I update everyday, once a day when I get home, but the pendings keep staking up. Sometimes I get credit after a task is complete, sometimes all i see is "pending." no compute errors or anything. the taks were successful. can anyone help?
-jrt

Welcome to SETI, I see this is your first post.

I just took a look at your Results/Tasks list. The pendings are nothing to worry about, they will get get credited when the quorum partner turns in their result. SETI needs 2 valid results on the same WorkUnit (WU) before credit is granted.

I did notice that you have a few Compute errors. These may be something to worry about if they occur frequently.
One of them had
SETI@home error -1 Can't create file -- disk full?
in checkpoint()
File: ../seti.cpp
Line: 400
Is your drive short of space?

---

Sir Arthur C Clarke 1917-2008

My advice is not to worry about it.

The first two pending credits that I have relate to WU's I finished on 20 September. That's a long time to wait for those who downloaded those WUs to get on and finish them. Is that not a worry?

---

flaming balloons

not even close to it. i have 148gb of freespace.

I don' understand why I have so many pendings. Can anyone tell me why I keep getting them? I update everyday, once a day when I get home, but the pendings keep staking up. Sometimes I get credit after a task is complete, sometimes all i see is "pending." no compute errors or anything. the taks were successful. can anyone help?
-jrt

Welcome to SETI, I see this is your first post.

I just took a look at your Results/Tasks list. The pendings are nothing to worry about, they will get get credited when the quorum partner turns in their result. SETI needs 2 valid results on the same WorkUnit (WU) before credit is granted.

I did notice that you have a few Compute errors. These may be something to worry about if they occur frequently.
One of them had
SETI@home error -1 Can't create file -- disk full?
in checkpoint()
File: ../seti.cpp
Line: 400
Is your drive short of space?

not even close to it. i have 148gb of freespace.

Have you only allowed seti to use to little disc space? See "your account" "general prefs, if you use the webbased prefs. If you use "local" prefs from the manager, then check there. My web based prefs look like this:

Disk and memory usage
Use at most 400 GB disk space
Leave at least
(Values smaller than 0.001 are ignored) 0.25 GB disk space free
Use at most 85% of total disk space
Write to disk at most every 600 seconds
Use at most 100% of page file (swap space)
Use at most
Enforced by version 5.8+ 100% of memory when computer is in use
Use at most
Enforced by version 5.8+ 100% of memory when computer is not in use

If you allow it to use too little disc space, that might result in those errors (I think)

The first two pending credits that I have relate to WU's I finished on 20 September. That's a long time to wait for those who downloaded those WUs to get on and finish them. Is that not a worry?

No - I have several that are at least a month older than that.

-Dave

---

My advice is not to worry about it.

The first two pending credits that I have relate to WU's I finished on 20 September. That's a long time to wait for those who downloaded those WUs to get on and finish them. Is that not a worry?

It is not a worry.

If the other machine crunching this work unit disappears (never returns the work) it will be assigned to someone else, and you'll get credit when they finish it.

---

My advice is not to worry about it.

The first two pending credits that I have relate to WU's I finished on 20 September. That's a long time to wait for those who downloaded those WUs to get on and finish them. Is that not a worry?

It is not a worry.

If the other machine crunching this work unit disappears (never returns the work) it will be assigned to someone else, and you'll get credit when they finish it.

Ah, OK. thanks. Do I get interest on my credit for waiting?

---

flaming balloons

Ah, OK. thanks. Do I get interest on my credit for waiting?

The only interest is in the guessing game of when they might arrive ;)

F.

---

Ah, OK. thanks. Do I get interest on my credit for waiting?

Only whatever interest you put into tracking it... ;)

Seriously though, what impact does that kind of thing have on the size of the result database? Does it have an impact on the time to back it up? Does it impact speed of queries due to having more rows, or are there really less rows? (wouldn't seem likely, but nobody is thinking beyond "I want my credit" at this point)...

would the value of the pending credit stabilize if you were crunching on alot of machines for a long time. That would be interesting to see...

---

Since Pending is a dynamic value without the use of any form of averaging,...I'd have to say NO to the "stable" part. It also changes based upon the types of AR's being sent. One could apply an "Average" to their pending (if they recorded such things) and make it appear to stablize (much like a RAC).

Here's my Pending since Aug 22nd (Note: I switched to stock app from optimized around 10/16). Additionally, I tested out all of simons apps during this period so my pending is more erratic than most would be.

This is what mine looks like:
--------------------------
Disk and memory usage
Use at most 100 GB disk space
Leave at least
(Values smaller than 0.001 are ignored) 0.001 GB disk space free
Use at most 50% of total disk space
Write to disk at most every 60 seconds
Use at most 75% of page file (swap space)
Use at most
Enforced by version 5.8+ 50% of memory when computer is in use
Use at most
Enforced by version 5.8+ 90% of memory when computer is not in use
--------------------------

not even close to it. i have 148gb of freespace.

Have you only allowed seti to use to little disc space? See "your account" "general prefs, if you use the webbased prefs. If you use "local" prefs from the manager, then check there. My web based prefs look like this:

Disk and memory usage
Use at most 400 GB disk space
Leave at least
(Values smaller than 0.001 are ignored) 0.25 GB disk space free
Use at most 85% of total disk space
Write to disk at most every 600 seconds
Use at most 100% of page file (swap space)
Use at most
Enforced by version 5.8+ 100% of memory when computer is in use
Use at most
Enforced by version 5.8+ 100% of memory when computer is not in use

If you allow it to use too little disc space, that might result in those errors (I think)

Jason, that should be plenty (Assuming your actually using the web based prefs and haven't invoked the local prefs by accident (which over ride web based prefs,, you would see the message in your message log if you did, it would say "Reading preferences override file" near the start of the log)(start of log means 20-30 lines down from the start of a fresh log session)

Ah, OK. thanks. Do I get interest on my credit for waiting?

Only whatever interest you put into tracking it... ;)

Seriously though, what impact does that kind of thing have on the size of the result database? Does it have an impact on the time to back it up? Does it impact speed of queries due to having more rows, or are there really less rows? (wouldn't seem likely, but nobody is thinking beyond "I want my credit" at this point)...

I'm just interested. I've had pending credits for months, years, and never given it a thought. I'm just happy to contribute and know that eventually I will get my credit. It's just that this thread came along and I thought I would find out what it was about. Which I am finding out, thanks to your and eveyone's answers. Cheers ;)

---

flaming balloons

um i don't know... what about this:

11/7/2007 9:41:49 AM||No general preferences found - using BOINC defaults
11/7/2007 9:41:49 AM||Preferences limit memory usage when active to 251.74MB
11/7/2007 9:41:49 AM||Preferences limit memory usage when idle to 453.13MB
11/7/2007 9:41:49 AM||Preferences limit disk usage to 9.31GB

Jason, that should be plenty (Assuming your actually using the web based prefs and haven't invoked the local prefs by accident (which over ride web based prefs,, you would see the message in your message log if you did, it would say "Reading preferences override file" near the start of the log)(start of log means 20-30 lines down from the start of a fresh log session)

um i don't know... what about this:

11/7/2007 9:41:49 AM||No general preferences found - using BOINC defaults
11/7/2007 9:41:49 AM||Preferences limit memory usage when active to 251.74MB
11/7/2007 9:41:49 AM||Preferences limit memory usage when idle to 453.13MB
11/7/2007 9:41:49 AM||Preferences limit disk usage to 9.31GB

Jason, that should be plenty (Assuming your actually using the web based prefs and haven't invoked the local prefs by accident (which over ride web based prefs,, you would see the message in your message log if you did, it would say "Reading preferences override file" near the start of the log)(start of log means 20-30 lines down from the start of a fresh log session)

Your preferences (above in blue) show 9.3 Gigabytes - way more than Seti, at least, actually needs... (depending on whatever other projects you may be attached to - that is a total BOINC figure, after all...) Whatever problem set off the "compute error", it was not due to lack of disc space.

---

.

Hello, from Albany, CA!...

To my way of thinking the pendings pile up for the simple reason that report deadline is too long. I have November 6th work units with a January 17th deadline. Guess we're covered for all the Commodore 64 users. :^)

Meow

---

To my way of thinking the pendings pile up for the simple reason that report deadline is too long. I have November 6th work units with a January 17th deadline. Guess we're covered for all the Commodore 64 users. :^)

Meow

Meow back at 'ya from the kitties!! You need a kitty avatar! Great handle.

But I must point out that the reporting deadline has little to do with pending credits. They depend on how soon you and your wingman both report the results on the WU in question (or in pending, or in quarantine, depending on how you look at it). The only impact reducing the deadline would have, I think, would be to increase the pendings, because if slower computers didn't meet the shorter deadline, the WU would then have to be reissued, thus restarting the clock on when it would be successfully reported by another user.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster