so, no disrespect, innovate innovate innovate, keep on going, looks great.
but.
In general terms - what does a potential user of this service conclude if the server appears to be hosted on a single machine and the admin staff doesn't seem to know how ulimit works?
(Yes, I realize this is ycombinator and about ideas and VC and all that.... just throwing the concept out there.)
Great product, but total lack of either understanding or preparedness on the lower levels.
It was unfortunate that this ulimit issue occurred and I apologise for that.
I knew about ulimit from 2 sources (a LinkedIn article on Node.js practices) and a 2nd source from a hosting service's documentation.
The fault (and it was mine) was that I didn't realise that in order to persist the ulimit setting between reboots, you had to set it in a configuration file.
Originally, the application was hosted across multiple instances and proxied, but due to the nature of the WebSocket library and it's use of transports with the proxy library, the connection was intermittent, so I reverted to a single instance. Since resolving the ulimit issue, this application has stayed up.
As for admin staff, you may be surprised to learn there is no company with multiple devs, designers, product people and sysadmin behind all this. This is all my work, all 2 and a bit months of it.
but.
In general terms - what does a potential user of this service conclude if the server appears to be hosted on a single machine and the admin staff doesn't seem to know how ulimit works?
(Yes, I realize this is ycombinator and about ideas and VC and all that.... just throwing the concept out there.)
Great product, but total lack of either understanding or preparedness on the lower levels.