> > > No we were talking about a database purge of units not returned and
> I
> > was
> > > explaining that purging after only 1 week of Berkeley down time was
> > > "premature".
> >
> > Ah, sorry. Still, a work unit can be pending for 6 to 8 weeks, easily.
> >
> Actually a unit can be re-issued up to a max of 15 times...that means that
> counting the inital time and allowing for 2 weeks for each re-issue, it could
> be 32 weeks before a unit is deemed uncrunchable. AND that assumes that
> berkeley is prompt about the re-issue timing.

Either way, significantly longer than a couple of weeks....

---

Is it normal to have workunits from the middle of January like this one: http://setiweb.ssl.berkeley.edu/workunit.php?wuid=7809944 (all 4 results were returned within the same few days)

My slowest computer has over 200 results and my fastest nearly 400.

---

> Is it normal to have workunits from the middle of January like this one:
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=7809944 (all 4 results were
> returned within the same few days)
>
HI, welcome to the Boinc/Seti Forums. I have nearly 200 old results dating back to Jan 11 2005. These have been validated and issued credit. To me they are dead and gone. having them still displayed gives me the chance to look back at my leisure and to see what my puters have done. They are of no other value to me or to Berkeley as far as i know.

If you read this entire thread, especially paying attention to the wise words of "Ingleside" you'll learn everything you ever wanted to know about this process.

To answer your question, "yes" it's normal. As to whether or not it should be this long???? well, it's up to berkeley. As I've said it's just historical data.

Again, Welcome to the forums.
hope this helps

tony

---

My perception (no way for me to verify) is that they have let the deleter program delete any finished/stored result files from older files, but have not run the program that removes database records of those completed/validated WUs.

The records for...say 4...results in the database is only about 4x65K or ~260K in database space plus some index overhead (each record has one 64K field for specific project use).

There are some records from way back on some of my hosts (Oct/Nov 2004), and the developers are aware of these, but frankly what benefit do they derive from crafting a sql script to get rid of them.