Nothing to worry about. They're just harder workunits.

You also have to remember that TC times are just estimates and the PCT complete for some projects (like FAAH) are just estimates because they are non-deterministic.

I found this one option on the WCG site for BOINC profiles to be very badly worded. On the WCG site it refers to this as how often to contact the site servers, but in the config XML file it is work_buf_min_days which doesn't really mean when to contact but only refers to buffering enough work for "x" time. The two meanings are not the same.

Does changing this option to 1 mean that jobs, when completed, won't be reported for up to 1 day as well, or does this setting not affect the reporting time?

Sek, when I saw the reference to the DCF, I remembered that you had discussed that in some of yor prior posts. Did a bit of searching and reading. Checked my client_state.xml file and saw:

<duration_correction_factor>2.030488</duration_correction_factor>

Looked back thru the messages tab and found the last benchmark run:

1/2/2007 12:18:36 AM|World Community Grid|Pausing task faah1119_d143n326_x1MEU_02_2 (removed from memory)
1/2/2007 12:18:36 AM||Suspending network activity - running CPU benchmarks
1/2/2007 12:18:38 AM||Running CPU benchmarks
1/2/2007 12:19:37 AM||Benchmark results:
1/2/2007 12:19:37 AM|| Number of CPUs: 1
1/2/2007 12:19:37 AM|| 1299 floating point MIPS (Whetstone) per CPU
1/2/2007 12:19:37 AM|| 2687 integer MIPS (Dhrystone) per CPU
1/2/2007 12:19:37 AM||Finished CPU benchmarks
1/2/2007 12:19:39 AM||Resuming computation
1/2/2007 12:19:39 AM||Rescheduling CPU: Resuming computation
1/2/2007 12:19:39 AM||Resuming network activity

Forced the benchmarks to run again (yea, I'll want to do that again late tonight to get that out of the daytime) and the benchmarks and DCF changed very minimally. As I understand this, my DCF says that my machine is taking twice as long as expected based on the benchmarks to complete WUs? I would presume that that is CPU time and not clock time? Right now, BOINC thinks my machine is over committed, probably because it went three days without getting any new work. I do recall that within the past week or so, I saw that one of the WU's I got was already marked valid for the other users. It looked like I was the fourth but within less than a minute of the WU being sent to me, it got sent to a fifth, then got its quorum thus showing as valid for those three and still as in progress for me. I aborted that WU as it didn't make any sense to me to crunch a completed WU. I believe that a day or two after that, I reset the project as the aborted WU wouldn't fall off the task tab in BOINC Manager. Given what I think I might understand from reading other posts on the DCF, I am starting to think I just need to give things a few days to crunch and see if things clear up and I get more realistic to completion times.

No, the 1 day is just the amount of work to buffer / contacting time. The due date, as reported in the tasks tab, is for WCG 7x24 hours i.e. u will not miss deadline, lest u do not complete/return within 7 days. Of the top of my head the title on the website profile is a BOINC standard and looking at the SIMAP one it says
If dabbling, please only do this in the override files, not the once controlled/updated from the website! The order of reading is the that the override files are read in last for that purpose.

Respective the DCF discussion of KH'.... the number is adjusted continuously and u need to let your machine alone, truly alone, for it does take weeks for BOINC to find it's balance. Whilst WCG has only one DCF for all it's projects and there for having an inherent issue, each DC has it's own DCF. e.g. my Tanpaku DCF is 1.05, the WCG is 0.8, the SIMAP is 0.85 and Rosetta 1.01.....guess who's doing the best flop estimations ;>)