Closed cccs-ip closed 10 years ago
jenkins is not yet installed on the new server.
It is hard to get a metric on responsiveness because it cuts across your client and the server. It typically takes me four to five seconds to shell in and I'm not seeing any performance issues at the shell once I'm connected - calling top does not indicate any resource issues on the server.
Try comparing another server response if you can shell in to something else. I'm not sure what is going on - I suspect that it is a local issue because I'm not seeing any performance issues from my (more distant) connection.
Thanks for checking the resources. I will close it now. I can ssh in almost immediately, but once in I am getting up to 2 second latency on the command line!
Crazy... I could not work with that latency. Something must be hammering your connection. Are you downloading movies or some such at the same time?
If yours is the only computer using your connection, those monitors we discussed a while back might be handy to see if there is unexpected network traffic going on.
Everything else is off (no downloads) and I am the only one home. Sometimes the internet here is bad... but who knows. I should check out the monitors.
If your family is like mine, there are laptops all over the place and kids who think it is cool to download the entire world's anime collection while they sleep or at school ;)
My terminal latency is very poor, even when working with no browsers open. Do we have anything on the server with high resource consumption (like Jenkins)? This issue is relatively new.. post-Jenkins, I believe.