4 ms·
He said there was high db latency. This matters a ton when your language is single threaded and not using async io. 20 queries would tie up the whole server for
by throwaway189262 6y ago
He said there was high db latency. This matters a ton when your language is single threaded and not using async io. 20 queries would tie up the whole server for a second at 50ms db latency.
You can get around it by using async instead of blocking, using fibers which don't block, or using a thread pool so other threads can keep serving.
I'm not experienced with Ruby but it sounds like Ruby doesn't do any of those
- dragonwriter 6y ago> I'm not experienced with Ruby but it sounds like Ruby doesn't do any of those Modern ruby can do any of those, though in 1.8 or earlier it could do fewer, and less well.
- sciurus 6y ago> You can get around it by using async instead of blocking, using fibers which don't block, or using a thread pool so other threads can keep serving. The typical approach for Ruby, Python, and similar languages is just to run more processes.
- throwaway189262 6y agoAh just like the 80's
- inopinatus 6y agoRuby does all of those things. The story sounds ancient, and even then a consequence of naive production design far more than any emergent property of language.