I am puzzled about some of the process statistics reported. For example, here is part of the the result of one that completed successfully.

Task 22245062

Server state 	Over
Outcome 	Success
Client state 	Done
Exit status 	0 (0x00000000)
Computer ID 	1511241

Validate state 	Valid
Credit 	0.00
Device peak FLOPS 	6.13 GFLOPS
Application version 	OpenIFS 43r3 Perturbed Surface v1.01
        x86_64-pc-linux-gnu
Peak working set size 	4,600.76 MB
Peak swap size 	4,974.33 MB    <---<<<
Peak disk usage 	1,221.20 MB

My machine has been up for over 11 days and has used, in total, only 164 Megabytes of swap space. On the other hand, it has 15992 MegaBytes of swap space allocated.

Since the "Peak swap size" is only slightly lager than the "Peak working set size" do I infer correctly that this number is only the amount of swap space that would be used if the process were completely swapped out? ... and that none of it has actually been used? I.e., should this line have a better name?

---

This figure most certainly shows peak virtual memory size, not swapped-out a.k.a. paged-out memory.

This figure most certainly shows peak virtual memory size, not swapped-out a.k.a. paged-out memory.

So they should rename it something like peak virtual memory size instead of its current name. But I do not suppose CPDN have anything to do with that name. Probably a Boinc (client) problem.

---

This figure most certainly shows peak virtual memory size, not swapped-out a.k.a. paged-out memory.

So they should rename it something like peak virtual memory size instead of its current name. But I do not suppose CPDN have anything to do with that name. Probably a Boinc (client) problem.

Correct, that number is the virtual memory size. As you explained nicely, it's the total size required if the process was completely swapped out of memory. It's a confusing choice of name which I think comes from the boinc client but I could be wrong.

Both client and server use the misleading nomenclature.
This gets onto the server's result.php web page:
https://github.com/BOINC/boinc/blob/master/html/inc/result.inc#L714

Boincmgr on the other hand says "Virtual memory size" in the [Properties] pop-up window of a task.

Come to that, it's buried pretty deeply in the fundamental design:

https://github.com/BOINC/boinc/blame/master/db/schema.sql#L321

If only this were the most important problem with the Boinc system. Then it would not matter whether they fixed it or not.

---