Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

2017-03-08 Thread McLeod, John 
Or if some other task needs high priority.

From: Jord van der Elst [mailto:els...@gmail.com]
Sent: Tuesday, March 7, 2017 3:40 PM
To: McLeod, John <john.mcl...@sap.com>
Cc: Robert Miles <robertmi...@bellsouth.net>; boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

What John is looking for is called "Leave Non-GPU tasks in memory when 
suspended", used to be "Leave applications in memory".
With this switched on, tasks that suspend keep their whole state in memory. 
With it switched off tasks that don't checkpoint start from the beginning, 
tasks that checkpoint start from the last checkpoint. But tasks that don't 
checkpoint usually don't switch out of memory until they're done. They can only 
switch out of memory when the user forces the task to do so (suspend), or by 
quitting BOINC.


-- Jord van der Elst.

On Tue, Mar 7, 2017 at 3:09 PM, McLeod, John 
<john.mcl...@sap.com<mailto:john.mcl...@sap.com>> wrote:
It depends.  If you suspend a task and return all the memory, then you lose any 
forward progress since the last check point.  There is a setting that allows 
the removal from memory (or at least there used to be), but I don't remember 
what it is.  A suspended task's memory can go to swap with no problem as it 
will not be touched until the next time that the task is resumed.

-Original Message-
From: boinc_dev 
[mailto:boinc_dev-boun...@ssl.berkeley.edu<mailto:boinc_dev-boun...@ssl.berkeley.edu>]
 On Behalf Of Robert Miles
Sent: Tuesday, March 7, 2017 8:22 AM
To: boinc_dev@ssl.berkeley.edu<mailto:boinc_dev@ssl.berkeley.edu>
Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

 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<mailto:y...@mailueberfall.de>>
> To: BOINC Developers Mailing List 
> <boinc_dev@ssl.berkeley.edu<mailto:boinc_dev@ssl.berkeley.edu>>,   BOINC
>   Projects 
> <boinc_proje...@ssl.berkeley.edu<mailto: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<mailto: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.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu<mailto: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.

___
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.

Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

2017-03-07 Thread Jord van der Elst 
What John is looking for is called "Leave Non-GPU tasks in memory when
suspended", used to be "Leave applications in memory".
With this switched on, tasks that suspend keep their whole state in memory.
With it switched off tasks that don't checkpoint start from the beginning,
tasks that checkpoint start from the last checkpoint. But tasks that don't
checkpoint usually don't switch out of memory until they're done. They can
only switch out of memory when the user forces the task to do so (suspend),
or by quitting BOINC.


-- Jord van der Elst.

On Tue, Mar 7, 2017 at 3:09 PM, McLeod, John <john.mcl...@sap.com> wrote:

> It depends.  If you suspend a task and return all the memory, then you
> lose any forward progress since the last check point.  There is a setting
> that allows the removal from memory (or at least there used to be), but I
> don't remember what it is.  A suspended task's memory can go to swap with
> no problem as it will not be touched until the next time that the task is
> resumed.
>
> -Original Message-
> From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of
> Robert Miles
> Sent: Tuesday, March 7, 2017 8:22 AM
> To: boinc_dev@ssl.berkeley.edu
> Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3
>
>  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.
> ___
> 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.
>
___
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.

Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

2017-03-07 Thread McLeod, John 
It depends.  If you suspend a task and return all the memory, then you lose any 
forward progress since the last check point.  There is a setting that allows 
the removal from memory (or at least there used to be), but I don't remember 
what it is.  A suspended task's memory can go to swap with no problem as it 
will not be touched until the next time that the task is resumed.

-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Robert 
Miles
Sent: Tuesday, March 7, 2017 8:22 AM
To: boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

 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.
___
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.

Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3

2017-03-07 Thread Robert Miles 

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 
To: BOINC Developers Mailing List ,   BOINC
Projects 
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.