Message boards :
Number crunching :
Length of Result List just dropped to way short -- why?
Message board moderation
Author | Message |
---|---|
TrevorS Send message Joined: 3 Dec 04 Posts: 21 Credit: 20,011 RAC: 0 |
A couple days ago each of my three machines had result lists that were in excess of 100 entries. Today they are down to 8 for my slowest and about 16 for my quickest (including the not yet returned results). Anybody know the reason? |
Astro Send message Joined: 16 Apr 02 Posts: 8026 Credit: 600,015 RAC: 0 |
try looking at the thread 4 down from this one. It's the same question/answer. hope this helps tony |
Pascal, K G Send message Joined: 3 Apr 99 Posts: 2343 Credit: 150,491 RAC: 0 |
They delete cleared results to keep the DB clean tidy and small....... Semper Eadem So long Paul, it has been a hell of a ride. Park your ego's, fire up the computers, Science YES, Credits No. |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
> A couple days ago each of my three machines had result lists that were in > excess of 100 entries. Today they are down to 8 for my slowest and about 16 > for my quickest (including the not yet returned results). > > Anybody know the reason? Look in the FAQ, I just added a topic on this ... look at the bottom when you enter the FAQ ... Also, do a site search on "File Deleter". |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
Uhm, not completely correct... ;) The way through the system is roughly like this: 1; When got atleast 3 "success"-results, Transitioner trigger Validator. 2; If wu passes validation, trigger Assimilator. 3; Assimilator copies the "canonical result" to the master science database. 4; Waits till all results is either reported and tried validated, or past their deadline. Trigger File_deleter if Assimilation done. 5; file_deleter removes all wu & result-files for this wu from the upload/download-disks. 5a; For this reason, any results returning later can't be validated, since there's nothing to compare against. 6; For seti, normally 7 days after #5, db_purge archieves wu/result-state to file, and afterwards removes them from database. 1-5 is normally always running, while db_purge isn't. BTW, you've also got an error under Quorum of results specifically "but if the result has been assimilated then no credit will be granted." |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
> Uhm, not completely correct... ;) > > The way through the system is roughly like this: > 1; When got atleast 3 "success"-results, Transitioner trigger Validator. > 2; If wu passes validation, trigger Assimilator. > 3; Assimilator copies the "canonical result" to the master science database. > 4; Waits till all results is either reported and tried validated, or past > their deadline. Trigger File_deleter if Assimilation done. > 5; file_deleter removes all wu & result-files for this wu from the > upload/download-disks. > 5a; For this reason, any results returning later can't be validated, since > there's nothing to compare against. > > 6; For seti, normally 7 days after #5, db_purge archieves wu/result-state to > file, and afterwards removes them from database. > > 1-5 is normally always running, while db_purge isn't. Ok, so where does this explanation go? I am not sure I know where you are saying that what has been said before is not correct. > BTW, you've also got an error under <a> href="http://boinc-doc.net/site-common/glossary/letter-q.php">Quorum of > results[/url] > specifically "but if the result has been assimilated then no credit will be > granted." I will make this fix |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
> > Ok, so where does this explanation go? I am not sure I know where you are > saying that what has been said before is not correct. > Well, maybe mis-read the faq, but from my understanding was that you was saying File_deleter was responsible for removing the wu/results from the database, when it's db_purge that is responsible for this... |
Dave Mickey Send message Joined: 19 Oct 99 Posts: 178 Credit: 11,122,965 RAC: 0 |
I understand that there are processes and programs in place to keep the db small, and they only keep results in the results list for a while, and that it's natural that results don't stay on the results page forever. But (like TrevorS seemed to be asking), I was wondering as well if anyone knows (just for curiousity's sake) what occurred in the last couple of days that drastically reduced the length of the results pages. I noticed that all (4) of my hosts pages shortened up quite a bit, too, in just the last day or 3. Anyone have insight on any recent changes that were made? (new computers?, more memory?, changed params in the servers?) Enquiring minds want to know.......... Dave |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
> Enquiring minds want to know.......... > db_purge hadn't been running since upgraded to the new BOINC db-server 10. February, and was turned-on again last week. Since purging normally is done 7 days after wu "done", means very many wu/results have been purged in a short time. As for waiting so long before starting after upgrade, most likely to test if any problems when the size of the database naturally would have increased when more users joins. It's much better any problems is catched before "classic" ends. ;) |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
Ingleside, Ok, I made an addition with the addition of the basic operational cycle. I probably, and almost certainly, do not have this linked in as much as it should be, but, at least it is in there ... If you, or anyone else, has a thought where this would help as a reference, let me know ... |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.