Rserve: Difference between revisions
(Created page with "Rserve Wiki == Properties == === Rserve running under Windows is very limited === For example, only one connection is allowed at a time. === Rserve needs to take double space …") |
|||
| Line 11: | Line 11: | ||
The R gui takes 0.7GB but Rserve uses 1.4GB. | The R gui takes 0.7GB but Rserve uses 1.4GB. | ||
=== Rserve has a limit of maximum size of a single REXP | === Rserve has a limit of maximum size of a single REXP === | ||
Maximum size of a single REXP: 2GB (on 32-bit platforms), theoretical limit is 2^55 on 64-bit platforms. | Maximum size of a single REXP: 2GB (on 32-bit platforms), theoretical limit is 2^55 on 64-bit platforms. | ||
Packet size is auto-adjusted, configured by maxinbuf and maxsendbuf config entries. (maximum 2GB) | Packet size is auto-adjusted, configured by maxinbuf and maxsendbuf config entries. (maximum 2GB) | ||
Revision as of 12:38, 22 October 2012
Rserve Wiki
Properties
Rserve running under Windows is very limited
For example, only one connection is allowed at a time.
Rserve needs to take double space compared to running under R gui
For example, x <- rnorm(450000*200) The R gui takes 0.7GB but Rserve uses 1.4GB.
Rserve has a limit of maximum size of a single REXP
Maximum size of a single REXP: 2GB (on 32-bit platforms), theoretical limit is 2^55 on 64-bit platforms. Packet size is auto-adjusted, configured by maxinbuf and maxsendbuf config entries. (maximum 2GB) The maxinbuf (max. packet from client to Rserve) and maxsendbuf (max. packet from Rserve to client) options in the configuration file allow you to set limits in order to prevent memory overflow on machines that act as servers for multiple connections. The defaults are 16MB and unlimited respectively.
So a statement like memory.limit(4000) does not help with the creation of 450000*200 double elements.