So.... look what can happen in a mere 1 week 4 days. I went from Zero to 11th place at Einstein, https://einsteinathome.org/community/stats/users.
Of course, things are still changing, and yesterday's numbers show an output of over 7 Million, so, it will probably go a little higher...especially if I get some of that Helicopter money from D.C.

And 18th place for a system.

I am pumping up just under 400,000 RAC on a 2 gpu Nvidia system (and loath to change to Amd/Ati from my Nvidia's). So it sure looks like any gpu-heavy system should be VERY productive.

Congratulations Tbar!

Tom

---

A proud member of the OFA (Old Farts Association).

So.... look what can happen in a mere 1 week 4 days. I went from Zero to 11th place at Einstein, https://einsteinathome.org/community/stats/users.
Of course, things are still changing, and yesterday's numbers show an output of over 7 Million, so, it will probably go a little higher...especially if I get some of that Helicopter money from D.C.

Congrats!
Join us on Rosetta too for a while :)

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

If I wasn't already in the GPU Usersgroup I would join. Sorry.

Tom

Same holds me on E@h. Already in Moon's SICITURADASTRA team.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Congrats!
Join us on Rosetta too for a while :)

Sorry, my CPUs are needed to run the GPUs. I'm not about to turn off 8 GPUs to run 8 CPU tasks. Now, if Rosetta can produce a GPU App that works similar to the SETI or Einstein NV Apps I'll give it some time.

BTW, the main GPU Host is up to #16 now, and should have clear sailing up to around #4.

Congrats!
Join us on Rosetta too for a while :)

Sorry, my CPUs are needed to run the GPUs. I'm not about to turn off 8 GPUs to run 8 CPU tasks. Now, if Rosetta can produce a GPU App that works similar to the SETI or Einstein NV Apps I'll give it some time.

BTW, the main GPU Host is up to #16 now, and should have clear sailing up to around #4.

Time for a MSI B360F-Pro MB and cpu (you can get an 8c/16t one) upgrade!



ROFLing.....


Sorry I could not resist. Actually if its not broke don't "fix it" !!!


Tom M

---

A proud member of the OFA (Old Farts Association).

It seems Rosetta isn't suitable for Android smartphones.
Even for those who can deal with its disk space and memory requirements.
https://boinc.bakerlab.org/rosetta/results.php?hostid=4069076
Too much time/energy is lost for nothing.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

It seems Rosetta isn't suitable for Android smartphones.
Even for those who can deal with its disk space and memory requirements.
https://boinc.bakerlab.org/rosetta/results.php?hostid=4069076
Too much time/energy is lost for nothing.

You can select how long it runs for, you can select the cache size, you can set when it does or doesn't process work so you don't end up with things like this.

Run time 1 hours 10 min 24 sec
CPU time 24 min 41 sec

So, if you want to have long runtimes and a huge cache, and the phone doesn't spend much of it's time actually processing BOINC work then most definitely- Rosetta is not the project for you.

and does the latest version of the Android BOINC Manager have the fix for this in it?

<message>
finish file present too long
</message>

?

---

Grant
Darwin NT

It seems Rosetta isn't suitable for Android smartphones.
Even for those who can deal with its disk space and memory requirements.
https://boinc.bakerlab.org/rosetta/results.php?hostid=4069076
Too much time/energy is lost for nothing.

You can select how long it runs for, you can select the cache size, you can set when it does or doesn't process work so you don't end up with things like this.

Run time 1 hours 10 min 24 sec
CPU time 24 min 41 sec

So, if you want to have long runtimes and a huge cache, and the phone doesn't spend much of it's time actually processing BOINC work then most definitely- Rosetta is not the project for you.

I reduced cache to 0.1/0 and runtime to minimal of 2h. Will see how this would help.
But not sure I understand how all this could help with cited runtimes.
Elapsed and CPU times depend exclusively from phone usage _and_ application (can it use CPU all time or waste much time on waiting for disk/memory), not from cache size or Rosetta's projected run time.

and does the latest version of the Android BOINC Manager have the fix for this in it?

<message>
finish file present too long
</message>

?

BOINC was installed on that phone week or two ago. So perhaps it has latest version. But I'll check for update.

EDIT: the reason of exit with error code at least for 2 tasks was "too much restarts". BOINC on Android can't prevent restarts by keeping stuff in memory. Just because BOINC get killed by itself from memory by OS. So if phone in active use restarts are inevitable.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I reduced cache to 0.1/0 and runtime to minimal of 2h. Will see how this would help.
But not sure I understand how all this could help with cited runtimes.

It will (eventually) help once Estimated times match reality and it uses the Fraction of time BOINC is running xxx% and While BOINC is running, fraction of time computing is allowed xxx% values to set the cache size.
And with the shorter runtime there would be less stops & restarts for a given Task- from memory it can be 5 or so minutes between Checkpoints, and that's on my i7-8700K. I've no idea what the biggest gap between checkpoints on a phone might be.
But with such a big difference between CPU time & Runtime even that may not be enough.

Elapsed and CPU times depend exclusively from phone usage _and_ application (can it use CPU all time or waste much time on waiting for disk/memory), not from cache size or Rosetta's projected run time.

Yeah.
Rosetta has a lot of disk activity at certain points during a Task.... and when starting & finishing a Task- so starting & stopping computation, frequently, really works everything hard. And with limited RAM (and even with lots of RAM in some cases) Leave in memory while suspended just is not an option.

So the only thing that comes to mind is the "Compute only between ---" option. It'll reduce the difference between CPU time & Run time, and end all the stopping & starting of the Tasks.


Even if Rosetta were to explicitly state their applications are not suitable for Mobile phones, people would still use them & complain. Or complain that they don't have an application they can use on their phone...

---

Grant
Darwin NT

3 day deadlines?
At least WCG gives one 7-10 days. :-)

3 day deadlines?
At least WCG gives one 7-10 days. :-)

The big problem is not just that 3 days, is the lack of stop points on some WU.
If for any reason you need to stop boinc (totally exit not just suspend) and restart you could loose hours of crunching for nothing.
That happening to me 2 days ago. I have a Roseta 4.15 running for >8 hrs (with about 80% done) and due a system update i was forced to reboot the host.
In my ignorance i take the usual steps. Totally exit boinc, and wait until it gives the ok i'm down. Then stop all services on the host and do the usual cold boot.
When everything was working again for my surprise, the task restart from 2 hrs approximately (at about 25%) loosing more than 6 hrs of crunching.
Looking on the Rosetta forum, there are a lot complains about this.

---

3 day deadlines?
At least WCG gives one 7-10 days. :-)

The big problem is not just that 3 days, is the lack of stop points on some WU.
If for any reason you need to stop boinc (totally exit not just suspend) and restart you could loose hours of crunching for nothing.
That happening to me 2 days ago. I have a Roseta 4.15 running for >8 hrs (with about 80% done) and due a system update i was forced to reboot the host.
In my ignorance i take the usual steps. Totally exit boinc, and wait until it gives the ok i'm down. Then stop all services on the host and do the usual cold boot.
When everything was working again for my surprise, the task restart from 2 hrs approximately (at about 25%) loosing more than 6 hrs of crunching.
Looking on the Rosetta forum, there are a lot complains about this.

Happened to me a couple of times. I shortened the run times to 4 hours so that I was less likely to lose any time. I'm only at rosetta for the covid, once that project is done I'm trying another project.

Even if Rosetta were to explicitly state their applications are not suitable for Mobile phones, people would still use them & complain. Or complain that they don't have an application they can use on their phone...

Haha, yes definitely will! :D :D :D
,

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Happened to me a couple of times. I shortened the run times to 4 hours so that I was less likely to lose any time. I'm only at rosetta for the covid, once that project is done I'm trying another project.

Same here. I will assign non-24/7 hosts to another "location" with shortest projected run time possible.
And stable "might" hosts will get longest possible projected run time to reduce start new task overheads.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I've been wondering what effect this news will have on the rest of the scientific community?

Will they ...
... see lots of skilled users with powerful computers, ready to take on a new area of science?
... mis-understand and read it (wrongly) as the beginning of the end of the BOINC platform as a whole?

. .Many are running out of work repeatedly because they are unaccustomed to such large numbers of volunteers :)

Stephen

:)

I'll go to a project that has an open source code for Nvidia GPUS and an off-line test suite similar to Seti@home.

. . Hey there Petri, nice to see you here.

. . Let us know if/where you set up shop, I for one will probably join you :)

Stephen

..

Open one "SETI orphans" Café or Pub in every country city where we have SETI@home participants :-)

Stephen

:)

Personally I was just pondering what I was going to do for this years WOW event. Whether in fact I would enter at all as it struck me last year as not very environmentally friendly.
Seems the decision has been taken out of my hands. I will crunch on my 4 main machines until there is nothing left to crunch, then I will be left with 5 750 Ti's, 2 1050's, 2 1060, and a 970 with nothing to do.
Whether I will crunch for another project remains to be seen, SETI was really the only one that ever interested me.

. . I thought you had a 1660ti as well? But I feel much like you. I have left three machines on E@H because it was my 'backup' project but I only do their tasks on the GPUs. To utilise the CPU I have tried Rosetta but had several issues there so I moved to WCG where I am not experiencing problems. But I do not feel the connection with either project (however worthwhile) that I have enjoyed with S@H.

Stephen

:(

About E@h:

I installed old NV 460SE GPU from another (currently disabled) host, but Einstein refuses to use it:

16/04/2020 22:28:15 | | CUDA: NVIDIA GPU 0: GeForce GTX 460 SE (driver version 365.19, CUDA version 8.0, compute capability 2.1, 1024MB, 950MB available, 746 GFLOPS peak)
16/04/2020 22:28:15 | | OpenCL: NVIDIA GPU 0: GeForce GTX 460 SE (driver version 365.19, device version OpenCL 1.1 CUDA, 1024MB, 950MB available, 746 GFLOPS peak)
and
16/04/2020 22:28:18 | Einstein@Home | Sending scheduler request: To fetch work.
16/04/2020 22:28:18 | Einstein@Home | Requesting new tasks for NVIDIA GPU
16/04/2020 22:28:32 | Einstein@Home | Scheduler request completed: got 0 new tasks
16/04/2020 22:28:32 | Einstein@Home | No work sent
16/04/2020 22:28:32 | Einstein@Home | see scheduler log messages on https://einsteinathome.org/host/11977460/log
16/04/2020 22:28:32 | Einstein@Home | Gamma-ray pulsar binary search #1 on GPUs is not available for your type of computer.
16/04/2020 22:28:32 | Einstein@Home | Gravitational Wave search O2 Multi-Directional is not available for your type of computer.
16/04/2020 22:28:37 | Rosetta@home | Sending scheduler request: To fetch work.
16/04/2020 22:28:37 | Rosetta@home | Requesting new tasks for NVIDIA GPU
16/04/2020 22:28:39 | Rosetta@home | Scheduler request completed: got 0 new tasks


So, what it needs?? OpenCL here... what app requirements then?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Einstein will do the same if you give it a small resource share, because it has a 7 day deadline. It insists on filling up to your cache size, then doesn't run for 5 days or so then panics and has to do more work than the resource share allows. Then come the Seti outrage and it would refill the cache, wash, rinse, repeat.

. . I am getting 14 day deadlines at E@H, 7 days I think at WCG and 72 hours at Rosetta. But as a backup I ran/run E@H with 0% resource share and I get 1 task at time so I have one waiting to report and one running. This works pretty well for me.

Stephen

:)