test with a browser and a server to try optimist, winston and general structure
browser client, send one message and get the echo.
socket.io client, parameters: number of clients and ramp up time -u -t, and logging with ps command. client sends-receives infinitely
socket.io client -u userCount -t timeRampup -n newMessageTimeout
Readme updated
client.js updated with parameter -l to indicate if it is a local connection or to amazon server
index changed to get cpu-memory values
prints min max mean elapsed time for a number of roundtrips
increase messageintervalperclient each 10 sec and then write to file
app.js -o to write server cpu mem details
client -t for message frequency
client -t -c will be executed for each concurrency level and message period. server data will be collected by sar tool
app.js printing frequency set to 1000
client counts for failed connecections, app can start with -p to watch process and cpu
server not call child process, client waits a minute after test
before going to sockjs
initial sockjs
initial websocket with just one connection of client
initial commit of websocket and redis
use json objects