does some of this history get "lost" or deleted over time? as in, is there some website where i can pull all the work units i've run in say the past year, and sort them by type? if not it's ok, I'm just curious if anything like this exists. I'm very much data driven with stuff like this. i like to see long timescale graphs.

BoincTasks has the ability to set the length of the History log save time before it drops older tasks off the list. It has a picklist setting from 1 day to 365 days. It also has the ability to make a backup of the History files for long term record keeping. It does have a "not recommended" warning on that feature but I assume it is simply because the storage requirement would be very large over a length of time.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

but i think the problem with this machine is certainly the extremely long run times. i'm going to pull the memory that i added to this system back out. its ECC, but possible that it's going bad

I find the Intel Memory Latency Checker a very handy tool to not only check the latencies of installed memory but also the transfer speeds. It's good for checking whether changes in memory timing or memory access were harmful or beneficial. It has both Linux and Windows applications.

intelr-memory-latency-checker

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

pulled the previously added sticks, and re-TIMed the CPUs (didnt check the temps before, but hottest cores are about 65C now).

whichever it was, it's all working fine now. time to see that RAC climb!

i think i'll add a 3rd 750ti to the Sierra-Spare system as well :)

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

The work units and results are only kept on the "live" database for twenty four hours after validation - there are a few tools that can help you get data in that time, but I wouldn't recommend doing it as the amount of data you will accrue over the course of a year is simply vast. You could try one of the BOINC manager tools or SETI Sprint and see if that does what you are looking for.

SETISpirit will archive BOINCs stdoutdae.txt file so that you could have years of data (for the daily/weekly/annual crunched graphs).
SETISpirit will also record the workunit details and results in it's own database. (Which can be sorted by application version)
It does not archive the actual workunits.

SETISpirit is a Windows-Only program.

(I think BOINCLogX does have the option to Archive the workunits) but it's no longer developed and is also Windows only

Further infomation about SETISpirit if interested

SETISpirit Thread (Annuncement/Discussion Thread)
SETISpirit Full Change log

Although I'd like to personally reccomend SETISpirit I have to Suggest BOINCTasks if you're wanting all your machines contribution history.

The work units and results are only kept on the "live" database for twenty four hours after validation - there are a few tools that can help you get data in that time, but I wouldn't recommend doing it as the amount of data you will accrue over the course of a year is simply vast. You could try one of the BOINC manager tools or SETI Sprint and see if that does what you are looking for.

SETISpirit will archive BOINCs stdoutdae.txt file so that you could have years of data (for the daily/weekly/annual crunched graphs).
SETISpirit will also record the workunit details and results in it's own database. (Which can be sorted by application version)
It does not archive the actual workunits.

SETISpirit is a Windows-Only program.

(I think BOINCLogX does have the option to Archive the workunits) but it's no longer developed and is also Windows only

Further infomation about SETISpirit if interested

SETISpirit Thread (Annuncement/Discussion Thread)
SETISpirit Full Change log

Although I'd like to personally reccomend SETISpirit I have to Suggest BOINCTasks if you're wanting all your machines contribution history.

does this tool only archive your contributions locally, from the time you start the program?
or does it pull already archived data from some database somewhere?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

BOINCTasks, and probably SETISprint, will only capture data from the time you start to use it. Getting data from the servers more than about 24 hours since validation time is just about impossible to the user as we don't have access to the storage servers.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

does this tool only archive your contributions locally, from the time you start the program?
or does it pull already archived data from some database somewhere?

Rob is right so yes from the time you begin using the program.

But I'll just clarify

It will use the local copy of stdoutdae [and the .old copy] to initally generate the graphs for the workunit statistics (daily[weekly]/monthly/annually)
SETISpirit can then archive the stdoutdae file.

eg you start using SETISpirit tommorrow [Late May] but the stdoutdae file begins in March. You'll have details about WU throughput from March.

The Analysis Results Table uses the AnalysisResults.db file that SETISpirit has to populate from observing the local BOINC Data Directory.
So you'll only get a record of work that is completed while SETISpirit is running.

SETISpirit basically will use its own copy of local data.