Skip to content
Prev 32208 / 398506 Next

how to run R as a daemon

On Mon, 19 May 2003, Laurent Faisnel wrote:

            
`more precise'?  At least some of the inefficiencies are emerging, but I
still have little picture of what you are actually trying to do.  It ought
to be possible to run a new R session in a well under a second (on a 1+GHz
machine):

gannet% time env R_DEFAULT_PACKAGES=NULL R --vanilla --slave < /dev/null
0.203u 0.039s 0:00.27 85.1%     0+0k 0+0io 1220pf+0w

for example (on a dual Athlon 2600, R 1.7.0).
It is, but waiting for instructions from one place (stdin or on a socket).
There is some danger of different jobs sent leaving things behind that 
will cause interactions.
You could just save and then load that matrix in your .RData
Yes, but it is your usage that is the problem.  You are mixing S3 and S4
methods (where did you copy an example like that from?).  You should
dump your scripts if you use S4 methods (which I don't think you should be
doing in such simple examples, nor if you care about speed):  see the
examples of S4-using packages on CRAN (e.g. DBI, SparseM).

Also consider upgrading to R 1.7.0 and setting R_DEFAULT_PACKAGES to what 
you actually need (and omit methods if you don't need it)