Luke,
sure, adjustment at run-time works just fine, the issue currently is that it is
baked-in at compile time so there is no way to adjust it (re-building R is not
an option in production environment where this usually happens).
That said, I'm still not sure that connection limit is a good w
We do need to be careful about using too many file descriptors. The
standard soft limit on Linux is fairly low (1024; the hard limit is
usually quite a bit higher). Hitting that limit, e.g. with runaway
with code allocating lots of connections, can cause other things, like
loading packages, to fa
Martin,
I don't think static connection limit is sensible. Recall that connections can
be anything, not just necessarily sockets or file descriptions so they are not
linked to the system fd limit. For example, if you use a codec then you will
need twice the number of connections than the fds.
> GILLIBERT, Andre
> on Tue, 24 Aug 2021 09:49:52 + writes:
> RConnection is a pointer to a Rconn structure. The Rconn
> structure must be allocated independently (e.g. by
> malloc() in R_new_custom_connection). Therefore,
> increasing NCONNECTION to 1024 should only use
RConnection is a pointer to a Rconn structure. The Rconn structure must be
allocated independently (e.g. by malloc() in R_new_custom_connection).
Therefore, increasing NCONNECTION to 1024 should only use 8 kilobytes on
64-bits platforms and 4 kilobytes on 32 bits platforms.
Ideally, it should b
> qweytr1--- via R-devel
> on Tue, 24 Aug 2021 00:51:31 +0800 (GMT+08:00) writes:
> At least in 2015, a github user, tobigithub, submit an
> [issue](https://github.com/sneumann/xcms/issues/20) about
> the error "Error in file(con, "w") : all connections are
> in use" N
