I am getting frequent but irregular disconnects from one of my VPSs with my VIP accounts, and I am desperate to figure out whi.
I have four VIP accounts (different brokers and retail and superannuation accounts) and three VPSs (ForexVPS, Beeks and W2Cloud). Whenever the VIP accounts are running on the W2Cloud VPS, I get disconnect messages.
I have pretty much eliminated the possibility it is CPU or RAM exhaustion: the following are plots of the RAM and CPU from the W2Cloud instance:
w2cloud-memory.png w2cloud-cpu.png
By comparison the ForexVPS instance runs a lot higher:
forexvps-memory.png forexvps-cpu.png
I think I have eliminated traditional network connectivity issues such as flapping routes: I used curl in a loop to access the HTTP service and ensure it was available. Even during an "outage" on the SimpleTrader service, the curl session works.
The same information makes me pretty certain it's not the SimpleTrader servers. Curl still works. This is further supported by the fact that during an "outage" the trade copying EAs don't appear to be attempting to connections to the servers. There is no SYN, SYN/ACK/ACK handshake. In fact there is no SYN.
I have a theory, albeit weak: There is some resource issue at the virtualisation layer. Maybe the physical machine is out of sockets or RAM or CPU or disk. It doesn't show up in the VPS monitoring itself because the VPS itself knows no better. The physical host needs to write to disk or something.
I don't really want a "Just use ForexVPS" answer. I like diversity, and the W2Cloud on paper and in practice, other than this disconnect issue, has better bang for buck.
I have four VIP accounts (different brokers and retail and superannuation accounts) and three VPSs (ForexVPS, Beeks and W2Cloud). Whenever the VIP accounts are running on the W2Cloud VPS, I get disconnect messages.
I have pretty much eliminated the possibility it is CPU or RAM exhaustion: the following are plots of the RAM and CPU from the W2Cloud instance:
w2cloud-memory.png w2cloud-cpu.png
By comparison the ForexVPS instance runs a lot higher:
forexvps-memory.png forexvps-cpu.png
I think I have eliminated traditional network connectivity issues such as flapping routes: I used curl in a loop to access the HTTP service and ensure it was available. Even during an "outage" on the SimpleTrader service, the curl session works.
The same information makes me pretty certain it's not the SimpleTrader servers. Curl still works. This is further supported by the fact that during an "outage" the trade copying EAs don't appear to be attempting to connections to the servers. There is no SYN, SYN/ACK/ACK handshake. In fact there is no SYN.
I have a theory, albeit weak: There is some resource issue at the virtualisation layer. Maybe the physical machine is out of sockets or RAM or CPU or disk. It doesn't show up in the VPS monitoring itself because the VPS itself knows no better. The physical host needs to write to disk or something.
I don't really want a "Just use ForexVPS" answer. I like diversity, and the W2Cloud on paper and in practice, other than this disconnect issue, has better bang for buck.
Comment