Hi David, A user on the BOINC forums reported that he was now getting ready to get rid of BOINC, because it would use his whole memory and then even more, swapping to page file and there was nothing he could do about it. (ref https://boinc.berkeley.edu/dev/forum_thread.php?id=11494)
He states to be running into this problem when running ATLAS GARL tasks, that use 2GB per task, which he appeared to run 10 of at the same time, using then 20GB of memory. A bit troublesome on a system using 16GB. So stopping that, he switched to LHC and running the LHCb simulation he now runs into to same problem. Here however there is a thread explaining why that is (https://lhcathome.cern.ch/sixtrack/forum_thread.php?id=4072): the LHCb tasks use 2GB of memory but report they only use 480MB per. So BOINC thinks they use 480MB, but they really do use 2GB. These all run in VirtualBox for as far as I understand, so perhaps that there's a bug in the wrapper how the memory usage is being read. In any case, shouldn't BOINC always poll the actual memory in use and stop using more when all of the available RAM has been consumed, even if there are free CPUs? Thanks, -- Jord van der Elst. _______________________________________________ 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.
