I am not sure if you can set the ulimit to 500K, the maximum number of outgoing connections cannot be more than 64K, A sure way of checking the ulimit under the right user and environment is by running the System.cmd "ulimit", ["-n"] from within your app and checking that value out. In the past, I’ve have had misconfigurations because the app was running as user foo whereas the ulimit was being updated for a user bar. As far as I know, a single app would have just one process which the beam would be running with 2 threads per core ( a normal scheduler and a dirty scheduler ), so not sure why you are seeing multiple processes.
minhajuddin
1
OvermindDL1
At least on Linux the file descriptor can be vastly significantly higher than 65k (I think it’s a tagged 32-bit handle, like 28 bits usable I think?).
0
steven7
sribe
Right, but I think he was implicitly referring to the max of 64k ports per IP. So yeah, there’s a possible limit of 64k, unless the last gateway before your server has multiple IPs it can use to connect, and the smarts to spread connections over them–I know this is a real thing, but no idea how common it is in practice. Or your server is directly exposed on the internet with connections coming from IPs all over the place, which I expect is quite rare for Phoenix apps.
0