From what I've seen, when BOINC suspends workunits, this DOES NOT free the
memory they are using.
It looks like BOINC should not be allowed to start a workunit without
checking
whether enough memory is still free, and it should then be required to
repeat
this check before starting the next one.
Date: Mon, 6 Mar 2017 21:27:47 +0100
From: yoyo <y...@mailueberfall.de>
To: BOINC Developers Mailing List <boinc_dev@ssl.berkeley.edu>, BOINC
Projects <boinc_proje...@ssl.berkeley.edu>
Subject: [boinc_dev] Boinc handling of workunits with much RAM
requirements
Hello,
I'd like to understand what Boinc does with workunits which require a
large amount of RAM.
I have workunits which require 10 GB RAM.
My understandig is, that only hosts which have at least 10 GB free RAM
are downloading them and only if 10 GB RAM are free they are started?
It is not clear for me what happens when the workunits are running and
if and how often Boinc checks their RAM consumption and what Boinc does
if they consume too much RAM.
A user blames, that he has a system with 8 cores and 16 GB RAM. This
systems has more than 10GB free RAM. So such workunits are downloaded
and started, 8 of them in parallel at the same time. After some seconds
all 8 workunits consuming 10 GB RAM each and the system is havily
swaping and nearly unresponsive.
Shouldn't Boinc find out, that too much RAM is consumed and suspend some
of the workunits?
Kind regards,
yoyo
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
