My favorites now, in order, are ClimatePrediction, WCG, Rosetta. I also am doing universe and milkyWay to soak up unused processors because ClimatePrediction sent me only one work unit in the last 4 months (Nov 7) that bombed out with invalid theta.

They're planning loads of new work very shortly, definitely for Linux, maybe also Windows under Virtualbox. I see you have a machine running each.

4 other users bombed on that work unit too. Except for that one, the last work unit I got from CPDN was at the end of July. I had about an 8-month gap in WCG work units. And Rosetta does not keep up with my machine either. I used to do Seti@home and Malaria, but they are gone.

I can max out all my machines with WCG. Sometimes I can't get enough GPU work, but only 1/4 of the time. All I changed was to make Boinc auto-retry downloads every 30 seconds, and to get 1+0.25 days buffer.

IIRC, none of those go faster than my connection.

Surely you do other things on the internet besides Boinc?

Store at least 0.50 days of work
Store up to an additional 1.5 days of work.

There are 5 projects. Is that really so large a cache?

For more than a couple of projects, yes.
The whole idea of a cache is to keep your system busy if a project has issues, and you are attached to only that project. The odds of all your projects having issues at the same time with that many projects is bugger all, so there is no need for a cache.

With more than a couple of projects, Store at least 0.05 days of work and Store up to an additional 0.01 days of work is plenty, and it means your Resource share settings will be met, much, much sooner.

---

Grant
Darwin NT

For more than a couple of projects, yes.
The whole idea of a cache is to keep your system busy if a project has issues, and you are attached to only that project. The odds of all your projects having issues at the same time with that many projects is bugger all, so there is no need for a cache.

With more than a couple of projects, Store at least 0.05 days of work and Store up to an additional 0.01 days of work is plenty, and it means your Resource share settings will be met, much, much sooner.

I have about 15 projects, but I only run about 4 at a time, and sometimes half those are ones with rare work. So I have a big cache so I get some of the rare work instead of just the other projects filling in.

Store at least 0.50 days of work
Store up to an additional 1.5 days of work.

There are 5 projects. Is that really so large a cache?

For more than a couple of projects, yes.
The whole idea of a cache is to keep your system busy if a project has issues, and you are attached to only that project. The odds of all your projects having issues at the same time with that many projects is bugger all, so there is no need for a cache.

With more than a couple of projects, Store at least 0.05 days of work and Store up to an additional 0.01 days of work is plenty, and it means your Resource share settings will be met, much, much sooner.

You think odds of my projects having issues at the same times are "bugger all?" I have that problem right now. No work units from CPDN since end of July, No work units from Rosetta in about a week. Spotty work from WCG. Having a queue of about a week might take care of Rosetta and now (after six months) WCG. But I do not like that. I much preferred when all these projects supplied work units whenever my Boinc-client asked for it.

---

That and backup projects should be set to 0% and not something like 0.xx%.

Can't do that with Milkyway, you get 40 seconds of work.

That highly depends on wether you ask for CPU or GPU work and also on your GPU, I'd get there at least 9.5 minutes of work for my GTX 275.

---

.

I have about 15 projects, but I only run about 4 at a time, and sometimes half those are ones with rare work. So I have a big cache so I get some of the rare work instead of just the other projects filling in.

I follow a different strategy: projects with rare work or overloaded servers (so in my case WCG & Rosetta) have obviously more than enough computing ressources at the moment, so i set them to NNT and allow new work from those, that can offer continuous supply with work, i.e. they actually need more computing power than they currently get.

---

.

I follow a different strategy: projects with rare work or overloaded servers (so in my case WCG & Rosetta) have obviously more than enough computing ressources at the moment, so i set them to NNT and allow new work from those, that can offer continuous supply with work, i.e. they actually need more computing power than they currently get.

That is a very interesting strategy. I must think more about it.

---

That is a very interesting strategy. I must think more about it.

Well, it has lots of advantages, for myself and the projects:

- I don't need to watch BOINC too carefully or even spend my time on pressing the retry button, forcing additional scheduler requests etc.
- I don't add load to already overloaded project servers
- I don't "steal" work from unattended computers without (working) backup projects, so less idle computers, more science done

Of course there are some limits for this strategy, Moo! for example was the last BOINC project supporting my HD3850, so even if it would have some issues, there was simply no other project to which I could move that GPU (except crunching directly for distributed.net of course). Users of for example Macs with Apple CPUs might face similar issues. But a standard x86_64 CPU running Windows or Linux can be moved nearly to any project.

---

.

That highly depends on wether you ask for CPU or GPU work and also on your GPU, I'd get there at least 9.5 minutes of work for my GTX 275.

Even my 10 year old 280X cards do a MW task in under 40 seconds.

- I don't "steal" work from unattended computers without (working) backup projects, so less idle computers, more science done

Not my fault Krembil can't get it's act together.

My GTX 1650 does Milkyway task in about 6 minutes.
That feeling when 2019 GPU is slower than 2013 gpu.

My GTX 1650 does Milkyway task in about 6 minutes.
That feeling when 2019 GPU is slower than 2013 gpu.

That's 93 GFlops. Mine is 1000. Nvidia sux. I have never and will never buy their low grade rubbish.

My GTX 1650 does Milkyway task in about 6 minutes.
That feeling when 2019 GPU is slower than 2013 gpu.

Well, Tahiti is High-End, the 280X has 250W TDP, GeForce 16 is the Low-End of Geforce 20 series, the 1650 has 75W TDP and it's launch price was half or (a lot) less of any of the Tahiti cards. Outside of that very special Milkyway application, the 1650 isn't bad at all, the SP Performance per Watt is even a lot higher.

---

.

Well, Tahiti is High-End, the 280X has 250W TDP, GeForce 16 is the Low-End of Geforce 20 series, the 1650 has 75W TDP and it's launch price was half or (a lot) less of any of the Tahiti cards. Outside of that very special Milkyway application, the 1650 isn't bad at all, the SP Performance per Watt is even a lot higher.

The SP is lower overall, I'm surprised they make a card that slow nowadays.

And DP is actually used in most of the projects, just not 100% of the time.

The SP is lower overall, I'm surprised they make a card that slow nowadays.

It's lower overall, but about 2.5x higher per Watt. That's a huge difference if you don't run Milkyway on it. Gaming performance (and that's what GPUs are actually made for, not for BOINC) is higher than Radeon HD 7970 GHz Edition, which burns 300W instead of the 75W the GTX 1650 is using. Yes, the Tahiti cards are great in particular for Milkyway and BOINC in general, but let's not act like that was what GPUs are primarily made for. It would be nonsense for the average GPU user to buy 2019 a Tahiti card when they can get better performance in games at about 25-30% energy consumption.

---

.

It's lower overall, but about 2.5x higher per Watt. That's a huge difference if you don't run Milkyway on it. Gaming performance (and that's what GPUs are actually made for, not for BOINC) is higher than Radeon HD 7970 GHz Edition, which burns 300W instead of the 75W the GTX 1650 is using. Yes, the Tahiti cards are great in particular for Milkyway and BOINC in general, but let's not act like that was what GPUs are primarily made for. It would be nonsense for the average GPU user to buy 2019 a Tahiti card when they can get better performance in games at about 25-30% energy consumption.

I play games, and I don't care for energy performance. It's not like I play games 24 hours a day. So as a gamer only the speed matters. And something a decade newer should not be slower. BTW, the Tahiti speed ain't good enough for games, I have a twice as fast Nano for that. Which is also efficient in power.

Hello there!

I use BOINC 7.9.3 on Ubuntu 18.04 and recently I have started to get errors on downloading files for Rosetta@Home tasks like "transient HTTP error".
It seems to affect only Rosetta's files, files for other projects seem to be downloaded well.
Just in case, the file names go as "KC_12mer_12_hallucinated..." and "KC_13mer_13_hallucinated..." for Rosetta 4.20.

It seems like I can download the files manually and place them where they should be (/var/lib/boinc/projects/boinc.bakerlab.org_rosetta/) - after that the task's status transitions from "Downloading" to "Ready to start".
However, I am afraid that there will be a similar problem with uploads - so may you please suggest how can I make BOINC manage Rosetta@Home files transfers automatically again?

Here is the event log with http_debug, http_xfer_debug and network_status_debug flags enabled - looks like is a kind of SSL certificate problem:

Tue 20 Dec 2022 10:35:55 EET | Rosetta@home | [http] HTTP_OP::init_get(): https://boinc-files.bakerlab.org/rosetta/download/7c/KC_12mer_12_hallucinated_55_11.zip
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS handshake, Certificate (11):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS handshake, CERT verify (15):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS handshake, Finished (20):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (OUT), TLS change cipher, Client hello (1):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (OUT), TLS handshake, Finished (20):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  ALPN, server accepted to use http/1.1
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  Server certificate:
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   subject: CN=www.google.com
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   start date: Nov 28 08:19:01 2022 GMT
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   expire date: Feb 20 08:19:00 2023 GMT
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   subjectAltName: host "www.google.com" matched cert's "www.google.com"
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:   SSL certificate verify ok.
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (OUT), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: GET / HTTP/1.1
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: Host: www.google.com
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.9.3)
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: Accept: */*
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server: Accept-Language: en_US
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Sent header to server:
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: HTTP/1.1 200 OK
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Date: Tue, 20 Dec 2022 08:35:56 GMT
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Expires: -1
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Cache-Control: private, max-age=0
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Content-Type: text/html; charset=ISO-8859-1
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Cross-Origin-Opener-Policy-Report-Only: same-origin-allow-popups; report-to="gws"
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Report-To: {"group":"gws","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/gws/other"}]}
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Content-Encoding: gzip
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Server: gws
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: X-XSS-Protection: 0
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: X-Frame-Options: SAMEORIGIN
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Set-Cookie: 1P_JAR=2022-12-20-08; expires=Thu, 19-Jan-2023 08:35:56 GMT; path=/; domain=.google.com; Secure
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Set-Cookie: AEC=AakniGOg4us7UbTeD0AIz-b37iy5EjS_ILng2YPon72NYT610HS15qt6Ru8; expires=Sun, 18-Jun-2023 08:35:56 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Set-Cookie: NID=511=HyJMAjp9f88XSRXcGz4s9sQAFWhAzMIrSpJaeSUC_skIKlJSsRvCrIMtIed6-zkZMwLD9-WodT8K9S2-9ePzMFIs65t46nnBtJ-nXtdLitjZgfv3qXVkPscnq9kBFN4CQf6JQinZl1JhCpUd1w3Gg-R2XDMF-YPh1RXirWlO2DI; expires=Wed, 21-Jun-2023 08:35:56 GMT; path=/; domain=.google.com; HttpOnly
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server: Transfer-Encoding: chunked
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Received header from server:
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1768 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 2850 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 3201 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 3689 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1485 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 8 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 286 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 5 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 9 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 6 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 5 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 4 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 2310 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http_xfer] [ID#0] HTTP: wrote 1211 bytes
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  TLSv1.3 (IN), TLS Unknown, Unknown (23):
Tue 20 Dec 2022 10:35:56 EET |  | [http] [ID#0] Info:  Connection #566 to host www.google.com left intact
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  TLSv1.2 (OUT), TLS alert, Server hello (2):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  SSL certificate problem: unable to get local issuer certificate
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  stopped the pause stream!
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#874] Info:  Closing connection 567
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] HTTP error: Peer certificate cannot be authenticated with given CA certificates
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  TLSv1.2 (OUT), TLS alert, Server hello (2):
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  SSL certificate problem: unable to get local issuer certificate
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  stopped the pause stream!
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] [ID#875] Info:  Closing connection 568
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | [http] HTTP error: Peer certificate cannot be authenticated with given CA certificates
Tue 20 Dec 2022 10:35:57 EET |  | [network_status] status: reference site lookup pending
Tue 20 Dec 2022 10:35:57 EET |  | Internet access OK - project servers may be temporarily down.
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | Temporarily failed download of KC_12mer_12_hallucinated_55_11.zip: transient HTTP error
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | Backing off 00:29:36 on download of KC_12mer_12_hallucinated_55_11.zip
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | Temporarily failed download of KC_12mer_12_hallucinated_55_11.flags: transient HTTP error
Tue 20 Dec 2022 10:35:57 EET | Rosetta@home | Backing off 00:25:01 on download of KC_12mer_12_hallucinated_55_11.flags
Tue 20 Dec 2022 10:35:58 EET |  | [network_status] status: online

With care, Viktor

I use BOINC 7.9.3

There's your problem, the latest version is 7.20.2, with much newer SSL stuff in it.

the latest version is 7.20.2, with much newer SSL stuff in it.

Where do I get the latest version for Ubuntu Linux?
I have tried to use one from BOINC's official website and I have got the next error:

/usr/bin/boinc: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/bin/boinc)

It turned out that the one there has even older version - 7.4.22 - good that I made a backup before.
The one which is available via bionic ppa is 7.9.3, the same version I have:

$ sudo apt-cache policy boinc
[sudo] password for sloboda: 
boinc:
  Installed: 7.9.3+dfsg-5ubuntu2
  Candidate: 7.9.3+dfsg-5ubuntu2
  Version table:
 *** 7.9.3+dfsg-5ubuntu2 500
        500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
        500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
        100 /var/lib/dpkg/status
     7.9.3+dfsg-5 500
        500 http://ua.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        500 http://ua.archive.ubuntu.com/ubuntu bionic/universe i386 Packages

This ppa should have 7.20.5
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc