kowsik

11 ms·

61.
by kowsik 15y ago
My observation/assumption is that your app is running in a multi-tenant PaaS environment, where mysteriously you start getting bind errors because the ephemeral port space is shared with other tenants.
62.
by kowsik 15y ago
Read the blog again. This is bollocks if you are running your own server where you can be multi-homed, add loopback aliases etc and crank up the memory to support 100,000+ sockets. I'm talking PaaS where your app is an multi-tenant enviro
63.
Speed Limit of PaaS - 64K TCP Ports(blog.mudynamics.com)
20 points by kowsik 15y ago|33 comments
64.
by kowsik 15y ago
try dyno-blitzer https://github.com/pcapr/dyno-blitzer which scales up dynos, runs a load test and tells you how many dynos you'll need to support x concurrent users.
65.
Test performance and scalability with blitz.io | Acquia(network.acquia.com)
3 points by kowsik 15y ago|0 comments
66.
by kowsik 15y ago
It's going to cost you no more than $79/day * 2 for two days of load testing if you sign up directly to http://blitz.io . That's peanuts compared to anything else on the market. And with EC2 lowering inbound bandwidth costs, this only gets
67.
by kowsik 15y ago
One more thing. An m1.small instance on EC2 (on-demand pricing) will cost you around $60/month + bandwidth costs. So you need a multi-tenant load testing solution to amortize the costs and drive hourly price down, which is what we are doing
68.
by kowsik 15y ago
Load testing is not a month-long event. Nobody does it 24/7 for 4 weeks straight. It's usually bursty for an hour or so of a day (aligned with a git push or continuous deployment), which bodes well for $1/hour http://blitz.io Heroku prici
69.
by kowsik 15y ago
The Heroku pricing is pro-rated to the second: https://addons.heroku.com/blitz
70.
by kowsik 15y ago
Yes, it's because they pro-rate add-ons by the second. If you sign up with Heroku, you immediately get 500 concurrencies as part of the free plan. Signing up directly with blitz.io, OTOH, gives you blogging and referral credits - see http:
71.
Load testing? Try to take down your app for $1 with blitz.io(gigaom.com)
28 points by kowsik 15y ago|10 comments
72.
Blitz.io: Scaling out Heroku apps for $1/hour(blog.mudynamics.com)
4 points by kowsik 15y ago|0 comments
73.
Blitz.io - How we use Heroku, AWS and CouchDB(blog.mudynamics.com)
53 points by kowsik 15y ago|0 comments
74.
Continuous integration with blitz.io(blog.mudynamics.com)
2 points by kowsik 15y ago|0 comments
75.
Blitz.io wins the best CouchDB app at CouchConf(blog.mudynamics.com)
10 points by kowsik 15y ago|0 comments
76.
by kowsik 15y ago
I had some serious issues with head.js with http://blitz.io in that the load order was not deterministic causing all sorts of weirdness. For example jQuery will end up loading after the code that requires jQuery resulting in undefined stu
77.
by kowsik 15y ago
this is pretty awesome!
78.
Blitz.io: Under the hood - how we use AWS, Heroku and CouchDB(prezi.com)
2 points by kowsik 15y ago|0 comments
79.
by kowsik 15y ago
I wrote this originally for an internal brown bag as a gentle introduction for SQL-oriented folks. Glad it helped!
80.
Using Google Analytics for Load Testing(secure.blitz.io)
2 points by kowsik 15y ago|0 comments
81.
Blitz.io: How many dynos do I need on Heroku(labs.mudynamics.com)
1 points by kowsik 15y ago|0 comments
82.
by kowsik 15y ago
Check the date on the article. :)
83.
by kowsik 15y ago
thanks for the delayed april 1st HN reference. Had fun writing this one! It's CouchDB's fault. :)
84.
by kowsik 15y ago
problem with most load testing tools is the fact that you have to script through them. It's a PITA. Especially with PaaS and Heroku/EngineYard/Other-Vendors/-style deployments, time-to-deploy often obsoletes the time-to-script-test-cases.
85.
by kowsik 15y ago
Thanks @pbreit and welcome to blitz.io. Check out the ruby gem (gem install blitz) for continuous integration and the chrome extension for in-browser load testing. And here's a quick blog on integrating blitz.io with @tropo so you can autom
86.
by kowsik 15y ago
Added gist comment.
87.
by kowsik 15y ago
Netflix streaming is like the bittorrent protocol (lots of participant hosts and lots of chunked fetches). See this: http://labs.mudynamics.com/2011/04/07/mommy-netflix-is-eatin...
88.
Page Optimization - It's just half the battle(labs.mudynamics.com)
2 points by kowsik 15y ago|0 comments
89.
by kowsik 15y ago
"elevated error rates" has got to be the BSOD of cloud panics. sigh Heroku had a similar issue yesterday.
90.
by kowsik 15y ago
As a PaaS vendor, they are supposed to abstract away from IaaS failures. And they were not to use a single region to host all their apps. I love Heroku and will continue to use them as long as I have the option to add affinity to my dyn

More ›