you agree.
John
From: R-help on behalf of Andy Jacobson via
R-help
Sent: Tuesday, December 14, 2021 8:59 PM
To: Henrik Bengtsson
Cc: Greg Minshall; Andy Jacobson via R-help; Andy Jacobson
Subject: Re: [R] checkpointing
I have been using DMTCP successfully
I have been using DMTCP successfully for a long-running optim() task. This is a
single-core process running on a large linux cluster with slurm as the job
manager. This cluster places an 8-hour limit on individual jobs, and since my
cost function takes 11 minutes to compute, I need many such
On Tue, Dec 14, 2021 at 1:17 AM Andy Jacobson wrote:
>
> Those are good points, Duncan. I am experimenting with a nice checkpointing
> tool called DMTCP. It operates on the system level but is quite OS-dependent.
> It can be found at http://dmtcp.sourceforge.net/index.html.
>
> Still, it would
Those are good points, Duncan. I am experimenting with a nice checkpointing
tool called DMTCP. It operates on the system level but is quite OS-dependent.
It can be found at http://dmtcp.sourceforge.net/index.html.
Still, it would be nice to be able to checkpoint calls within R to potentially
ey start up again after a normal reboot, are able to continue almost as if
nothing had happened.
-Original Message-
From: R-help On Behalf Of Jeff Newmiller
Sent: Monday, December 13, 2021 11:54 AM
To: Andy Jacobson ; Andy Jacobson via R-help
; r-help@r-project.org
Subject: Re: [R] check
Use VirtualBox. You can take a 'snapshot' of a running virtual
machine, either from the GUI or from the CLI (vboxmanage snapshot ...)
and restore it later.
This requires NO changes to R. Snapshots can be restored on
another machine of the same kind with the same system software.
VirtualBox is
I used to work on a Prolog implementation that did something similar.
At any point you could explicitly save a snapshot of the current state
and then from the operating system command line, resume it.
This wasn't really for checkpointing. It was so that you could load
up a customised environment,
Duncan,
> R functions can call libraries written in other languages, and can
> start processes, etc. R doesn't know everything going on in every
> function call, and would have a lot of trouble saving it.
indeed, that obvious fact hadn't occurred to me. i withdraw my
contention. :)
cheers,
On 13/12/2021 12:58 p.m., Greg Minshall wrote:
Jeff,
This sounds like an OS feature, not an R feature... certainly not a
portable R feature.
i'm not arguing for it, but this seems to me like something that could
be a language feature.
R functions can call libraries written in other
Jeff,
> This sounds like an OS feature, not an R feature... certainly not a
> portable R feature.
i'm not arguing for it, but this seems to me like something that could
be a language feature.
cheers, Greg
__
R-help@r-project.org mailing list -- To
This sounds like an OS feature, not an R feature... certainly not a portable R
feature.
On December 13, 2021 8:37:30 AM PST, Andy Jacobson via R-help
wrote:
>Has anyone ever considered what it would take to implement checkpointing in R,
>so that long-running processes could be interrupted and
Has anyone ever considered what it would take to implement checkpointing in R,
so that long-running processes could be interrupted and resumed later, from a
different process or even a different machine?
Thanks,
Andy
--
Andy Jacobson
andy.jacob...@noaa.gov
NOAA Global Monitoring Lab
325
12 matches
Mail list logo
