Just a notice to Stefan, only a few days left of CPU WUs in the queue.

Thanks, I noticed :) I'm in the process of creating new WUs but the issue is that they are more demanding than the last ones so we are trying to figure out ways to make them use less disk at the cost of more computation time because the largest one used 50GB of scratch space to calculate.

My HP Linux laptop running SuSE Leap 15.0 after Leap 42.3 (any relationship to SLES 15.0 ?) has 752.37 GB available to BOINC. Instead my older SUN WS running SuSE Leap 42.3 has at most 30 GB available to BOINC 7.8.3 of a 1 TB disk.
Tullio

So the ones I am sending out now should use maximum around 6GB scratch space on /tmp/. If you hit any problems feel free to report here.

Minor note: barring changes I am unaware of, the scratch space used during the run is in the slot directory. (/tmp is limited on many systems)

I have a QC task running on my Linux laptop. It is at 73% after 9;07;27 hours. But its slot is empty.
Tullio

Two QC tasks failed on my main Linux box which has a 30 GB limit to BOINC 7.8.3 with the same message DISK USAGE LIMIT EXCEEDED. GPU task running fine on its GTX 750 Ti at 61 C.
Tullio
Same error after 55 minutes also on the laptop despite the 750 GB available to BOINC. But where is that scratch file? I cannot see in either in /tmp or /var/lib/boinc/slots.

---

OK I have a feeling we hit a file-size limit of BOINC and not of the drives. I'll chat it up with Toni and see what we can do.

For the moment I'll cancel them since they nearly all fail with the same disk usage error.

OK I have a feeling we hit a file-size limit of BOINC and not of the drives. I'll chat it up with Toni and see what we can do.

For the moment I'll cancel them since they nearly all fail with the same disk usage error.

Every workunit sent out by a BOINC server has an associated value

<rsc_disk_bound>

(in bytes). That value - set by the project - has to be large enough to accommodate all anticipated disk usage. If you use more than you've declared in advance, 'DISK USAGE LIMIT EXCEEDED' is exactly the error message you'd expect.

Completed and validated two QC task on my main Linux host. A GPU task is running on it at 1202 MHz clock,5400 MHz memory transfer, temperature 61 C on its GTX 750 Ti, driver 384.111.
Tullio

---

Completed and validated two QC task on my main Linux host.

It's really too bad that QC is not available for Windows :-(

just get Linux installed.

Two more QC tasks completed, two ready to start. Thanks.
Tullio

---

CPU usage reaches 197% on my old Opteron 1210 with 2 cores, 145% when a GPU task is also running. RAM is 8 GB.
Tullio

Sorry, but these are still the same old QC jobs. Thanks for the reports but it should not have changed much. I had to put some more of the old ones on queue while we fix the app space configuration so that I can send the new "SELE*" workunits.

I canceled remaining QMML50_2 jobs because I found out that some of them might be duplicates of already calculated WUs since there was a minor issue when retrieving them which left some behind. I am redoing the calculation of missing WUs now to make sure the ones I send out are correct. It might take me a day so please be patient.

SELE2 WUs are being sent out now. Toni increased the allowed space of the app to 30GB. From my tests the WUs should not use more than 6GB space each (the largest molecule). If you run many in parallel you might hit the limit though? I'm not certain about that.

Let's see how it goes this time!

CPU usage reaches 197% on my old Opteron 1210 with 2 cores, 145% when a GPU task is also running. RAM is 8 GB.
Tullio

Wouldn't it be more energy efficient to run a newer CPU? It's 100W for 2 Cores @ 1Ghz.

Unless your electricity is free :D

---

new WUs don't seem to work: they consume a lot of memory, throw computation errors or just rest at 10% progress forever.

I see 89 successes and 17 errors. Seems ok for a start. I'll look into the errors but they don't seem to be broken as a whole.