News for hackers. Stuff that matters.
Re:Optimizing AngularJS by NKCSS on Friday November 01, 2013 @04:28AM (#6652480)
Your link gives a 502
Re:Optimizing AngularJS by DigitalSea on Friday November 01, 2013 @06:32AM (#6652852)
Haha yeah, it received 12,000 clicks in the space of about 1 hour or so which took it down. Node is good, but it couldn't handle that many clicks.
Re:Optimizing AngularJS by mnutt on Friday November 01, 2013 @09:28AM (#6653512)
Isn't that about 3 clicks a second? Was there a database issue?
Re:Optimizing AngularJS by DigitalSea on Friday November 01, 2013 @06:02PM (#6656790)
It seemed the server at times would get hammered and there would be a kind of race condition happening causing a variable for the clicks I am incrementing to have a value of undefined at times (no idea). I was using nodemon instead of forever.js, so when the error would occur, it wouldn't restart. It's all good now.
Re:Optimizing AngularJS by senorprogrammer on Friday November 01, 2013 @09:49AM (#6653672)
On average. I suspect his clicks were bursty.