I was thinking of how in works, at least in Windows, when you launch BOINC with CPU affinity. It launches all child processes with the same affinity.

Ah, I see. Is it any tool in Android to see process/thread affinity like in Windows?

Anyway when the phone is idle (second picture) i see only one core seems active, while when running BOINC (first picture) it seems all are active.
Cheers

That's how should be in case each task crunched on own core andphone uses all his computation nodes for crunching.
in my case 2 tasks launched by BOINC but only 1 CPU of 2 remains active.
So, each task takes ~2 times more elapsed time than CPU time to process and phone itself operates as single core devices.

Maybe the manufacture has limited each process that starts to only use one processor with some kind of processor affinity command.
Based on the behavior you have described that seems like something that may be occurring.

But cause BOINC launches 2 tasks there are 2 independent processes actually. Still they both use CPU 0 and CPU1 get switched off soon I stop touching the screen.

Anyway when the phone is idle (second picture) i see only one core seems active, while when running BOINC (first picture) it seems all are active.
Cheers

That's how should be in case each task crunched on own core andphone uses all his computation nodes for crunching.
in my case 2 tasks launched by BOINC but only 1 CPU of 2 remains active.
So, each task takes ~2 times more elapsed time than CPU time to process and phone itself operates as single core devices.

Another point of comparison:

Host 8398355, currently running S@H and pogs.
[EDIT: Android 5.1.1, LG LTE model K330, in case the host info eventually gets deleted.]

Per CPU-z all 4 cores are running 97-100% at 998 MHz on wall socket, 95-99% at 1094 MHz on battery; listed range being 200MHz to 1.09 GHz

From an example WU: Wall Clock=85,532.95, CPU time=83,848.01 [seconds]

And I vaguely remember that it doesn't do Hyperthreading, but I'm forgetting how I found out.

No luck on the Xeon. Maybe I should install the resceduler and see if that helps. Or do I have to have at least one CPU already?

I have only got GPU tasks. Anybody got anything for CPU?

Anybody any thoughts on how quick the RAC should recover after the outage? Mine was quick to drop but has not shown much sign of recovery despite crunching 100% since Saturday morning.

I'm off by 3 days, but Happy Birthday Me, WooHoo, Cheers!

Yes things have changed, About 8 months ago I fired up an old 133MHz cpu, and what pops up ... Seti3, LOL, if I could have got a network card to work I would have tried reporting the 1 task that was remaining :D

I have ordered with Amazon a treadmill to exercise my legs. I received a big package containing the treadmill and a manual. The manual referred to an electric motor which I could not find in the package. Since it was on Sunday i coud not phone the firm to ask why. So I went to the website, found a blog and discovered that the model I had bought had no electric motor, only a rotating wheel. They had sent me the wrong manual. This happened often when, buying a computer or a printer you got also a manual. Now all you get is a leaflet which gives you some instructions in 20 languages. If you need a manual you have to search for it on the Web.
Tullio

Which, again, is in fact not the science database that runs informix .

Is this along with each's systems OS and primary DB documented anywhere?

Since the issue is with the SETI@home science database and not the master or replica databases I'm not sure how how the deadlines would even be relevant.
Given the data is stored in the science database after it has been validated.

The reason for the serverside limits was due to the load on master database and it falling over or just plain getting bogged down.

I too have wondered why SETI has stuck with the extremely long deadlines I assess were implemented for the original hardware used on the project. That kind of hardware is 18 years in the past and does not need to continue to be supported. I agree with you Jeff, I would expect the sizes of databases and the strain they put on the project would be greatly lessened if the deadlines were reduced by a month, lets say from the current 2 month deadline.

As I understand it, the reason there has been no adjustment is because Eric does not wish to disenfranchise anybody from participating in this project.

And that would include folks with very meager hardware resources. Not everybody can afford what some of us are able to.

That is why.

From the Informix site:

Fast, Always-on Transactions

Provides one of the industry’s widest sets of options for keeping data available at all times, including zero downtime for maintenance.

Eric mentioned Informix, which I suspect is IBM's Informix DB, probably waiting on a new build from them. Or at minimum awaiting an undocumented config switch as a temp work-a-round. There was some backend working happening last night, perhaps they gave it a go and ran into further issues.