4 ms·
"There's no reason that it can't be handling other requests while waiting for a DB response or a pipe." Concurrent request processing most likely belongs in th
by ubernostrum 17y ago
"There's no reason that it can't be handling other requests while waiting for a DB response or a pipe."
Concurrent request processing most likely belongs in the server, not in the application.
"Scaling Rails is a nightmare."
For someone who complains of "well-trodden ground" in others' arguments, you certainly seem to have a deeply-rooted belief in the myth that particular languages and/or frameworks "scale" or "don't scale".
- deleted 17y ago[deleted]
- deleted 17y ago[deleted]
- timr 17y agoIs it a still just a belief in a myth if you've experienced it first-hand?
- ubernostrum 17y agoOK, so show me a language or framework which has a button you push, or something similar, to scale without any hassle.
- timr 17y agoThe lack of a push-button solution for all scaling problems does not mean that Rails doesn't suck at scaling.
- ubernostrum 17y agoSo how do you figure that it sucks? And don't say "Ruby is too slow" or I really will write you off as reciting tired old myths.
- timr 17y agoWrite me off if you like, but here's a short list (just off the top of my head) that we've encountered while trying to scale Rails: Rails has terrible support for database replication (we've had to roll our own). Its caching architecture is laughably bad, and the implementation was/is buggy (again, we rolled our own), and there's next to no support for the kind of robust page cache expiration mechanisms that are necessary to run a large, dynamic site (Observers are only a start). Rails is a memory hog, takes too long to start, has poor translation and locale support, and simply passing a request through ActionController adds huge overhead that cannot be escaped. And even though you don't want to hear it, Ruby is slow -- even after working around all of the above, we still had to implement a fast page caching layer just to work around the general, all-purpose slowness of Ruby. But like I said, write me off if you want.
- ubernostrum 17y agoSeems like you're picking things which are difficult to deal with no matter the language/framework your application code is written with -- DB replication, cache invalidation, etc.