kowsik

21 ms·

31.
by kowsik 14y ago
Very cool - just a few weeks ago, I spent two weekends (8 hours total) building https://www.delayed-tweets.com . Sinatra on Heroku + Stripe along with a bunch of gems to connect up to Facebook, Twitter and LinkedIn. It's mainly for my pers
32.
MTTR over MTBF - The joys of deploying cloud apps(blog.freeradical.me)
1 points by kowsik 14y ago|0 comments
33.
Why every enterprise app developer should work on a SaaS(blog.freeradical.me)
2 points by kowsik 14y ago|0 comments
34.
Performance Testing Rails with BlitzIO(schneems.com)
5 points by kowsik 14y ago|1 comments
35.
Why the cloud is bad for startups(blog.mudynamics.com)
1 points by kowsik 15y ago|0 comments
36.
by kowsik 15y ago
Regarding ease of use, if you are a dev, there's always toto or jekyll. Throw in disqus for commenting and you are pretty much done. Each blog is just a simple haml/erb/liquid template and git push is all you need to get a new page/blog up.
37.
NoOps, ShmoOps and Somebody Else’s Problem(blog.mudynamics.com)
3 points by kowsik 15y ago|0 comments
38.
Blitz.io: New Relic as an Analytics plugin(docs.blitz.io)
2 points by kowsik 15y ago|0 comments
39.
by kowsik 15y ago
I've been writing C and C++ for a long time (kernel and user mode) and what I find is, it takes a fair bit of discipline when writing C++ code (like hiding new/delete for stack-only objects or ensuring operator= works for heap objects and s
40.
by kowsik 15y ago
You can find out with dyno-blitzer: https://github.com/pcapr/dyno-blitzer
41.
Blitz.io: Using redis transactions with CouchDB(blog.mudynamics.com)
1 points by kowsik 15y ago|0 comments
42.
Dear Angry Nerds, meet Blitz the Bird Thrower(blog.mudynamics.com)
1 points by kowsik 15y ago|0 comments
43.
Blitz.io: Geo-located traceroutes(blog.mudynamics.com)
1 points by kowsik 15y ago|0 comments
44.
Blitz.io is now available as a CloudFlare app(blog.mudynamics.com)
2 points by kowsik 15y ago|0 comments
45.
by kowsik 15y ago
the cedar stack has a writeable file system, though no persistence across dyno recycles/restarts.
46.
by kowsik 15y ago
See this: http://blog.mudynamics.com/2011/09/05/help-couchdb-break-the... for various server tuning (not really CouchDB-specific). You can change the net.ipv4.ip_local_port_range to "1024 65535" to increase this range.
47.
Help CouchDB break the C10K barrier(blog.mudynamics.com)
2 points by kowsik 15y ago|0 comments
48.
by kowsik 15y ago
Read this thread first - http://news.ycombinator.com/item?id=2945185
49.
Blitz.io - Path-finding with CouchDB(blog.mudynamics.com)
3 points by kowsik 15y ago|1 comments
50.
by kowsik 15y ago
Here's the blog on what we are learning as we scale: http://blog.mudynamics.com/2011/09/01/blitz-io-path-finding-...
51.
by kowsik 15y ago
I can only speak for http://blitz.io . We generate an account-specific UUID which becomes a URL that you need to make available on your app (adding a route in ruby/node.js or uploading a txt file). Before each load test we check that your
52.
by kowsik 15y ago
thanks for the vote of confidence, will write up what happened soon.
53.
by kowsik 15y ago
sorry, we had a glitch this morning when one of our db clusters went offline - had to reroute all traffic to our other cluster - all good now.
54.
by kowsik 15y ago
You have to think about concurrency. If there were a total of 64K simultaneous requests to that physical instance, each of which is running 100+ apps because it's multi-tenant, this drastically reduces the number of ports available to each
55.
by kowsik 15y ago
thank you, thank you! whew Hopefully the new picture on the blog clarifies which ports I'm talking about.
56.
by kowsik 15y ago
Talking about port exhaustion is, I realize, a little confusing because there are the web requests coming in and the web-tier is making outbound requests to other services. Adding an image to the blog to hopefully clarify things.
57.
by kowsik 15y ago
I've added a picture to clarify which ports I'm talking about. Hopefully this clarifies things a bit.
58.
by kowsik 15y ago
My point is the thing you are connecting in the back-end has to scale at the same level as node - if not better. I'm sure making independent non-pipelined requests to CouchDB will help, but if CouchDB views are slow or it can't handle the c
59.
by kowsik 15y ago
We had a node.js app where each inbound request would go through a set of HTTP connections to the back-end couchDB. When the concurrency reached around 1,000 then there were 1,000 requests made through 10 couchDB pipelined connections. The
60.
by kowsik 15y ago
Okay, we are talking past each other. If you have a server on an EC2 instance, with enough RAM you can support more than 64K inbound connections for exactly the reasons you mention. Try generating more than 64K connections outbound and

More ›