New tasks came down about an hour ago

Now out of work new

This has been the best run we've had for a couple of years - bound to end at some point once everyone's offline cache runs down.
It's at this point my 12hr runtime setting ekes out my remaining work as far as possible.

What I'd re-emphasise is that the default runtime for tasks has fallen to 3hrs for some reason, which I believe to be a mistake and contradicts the forced Boinc setting of 8hrs,
As such, people should go into Boinc's Your Account option, select Rosetta@home preferences and change Target CPU run time to an explicit 8hrs rather than "not selected".
This will almost treble how long tasks run and extend the life of work batches so that we run out less, if at all, while almost trebling the credit we get for tasks too.

This should be considered a high priority for everyone imo.

But for anyone else that's been reading these posts...

If you limit the number of cores/threads available to BOINC, you will maximise your BOINC processing. You will get the maximum possible amount of work done each day that your system is capable of, you won't have issues with deadlines (unless of course you have inappropriate cache settings), or Panic Mode or any of those types of issues.

Well, that's obviously not true.
If you limit the number of cores available to Boinc, your Boinc processing will be limited to the maximum # of cores you've allocated, while your unallocated cores won't be used for Boinc and may or may not be fully utilised, depending what else is going on.
Use all your cores all the time. Your computer will decide millions of times per second what it should do with its capability better than any human ever will.
Do not listen to the man behind the curtain.

You ran out of memory. Six jobs of 2.6 GB and you have 16 GB.

I'd like to comment.

I see a problem, a problem that I should not be seeing. I try to make headway to resolve it, so ask. The result of asking each time is the same, basically, the BOINC folk tell me the problem is Folding, the Folding folk tell me it is not.

I have set no new tasks at both. I would seem to face a choice, I can support one or the other. Both are important to me.

28 tasks with validate error...great....but i suppose thats just the way it goes with a beta.

I hope I got what you wanted this time. I rebooted, started BOINC with a watch in hand, counted five minutes and then got the log file.

Thanks.

Your confusion appeared to be in thinking that a WU had a time allocated to it

No, I didn't mean that either.

I continue not to see rosetta@home in the list of the projects....

I'm sorry, but neither answer directly responds to my question.

Maybe my question wasn't clear enough, but I'm asking the meaning of TQJ given the variable sizes, not what a work unit is or how long the server will take to process work units.

I tried again after doing a reset and got computation errors for each task after under a minute. Is there anything else I can do to debug?

How do I interpret the server status page?
Today it says "Total queued jobs: 431,868"

For most projects one job is one work unit, but here we have variable work unit sizes creating multiple models apiece.
My 36 hour work units have hundreds of models, and the beta ones have thousands.

The lowest common denominator is a two-hour work unit.
So are the total queued jobs 863,736 hours of work?
Are they 431,868 models of various complexity, completed in minutes to hours apiece?
Are they part of a pool with the in-progress models, totaling 717,885 iterative calculations bouncing between users until they reach a undisclosed limit and retire out of the pool?

As I said, Folding has been running on this machine for years, the "problem" I started the thread about is VERY recent. All the tasks from that last download have completed and returned now, they show quite a variety of run times 73K to 90k. There are also other tasks downloaded the same day, but at an earlier time, that do not show the extended run time.