throw_aw100's comments

On: The Mythical IO-Bound Rails App

[throw_aw100]

I don't want to be a "back seat driver", but it seems strange to me as well.

It could be that the original files are used by other processes, and that they for some reason don't want to create two separate files. Maybe an issue with office politics (works on a different team), or an attempt at saving disk space

On: The Mythical IO-Bound Rails App

[throw_aw100]

I don't have experience with Rails, but I have experience with the other runtimes.

I read their comment as needing an external database pool to scale, not that they don't need a pool.

When running JVM or the other runtimes, the database pool can be part of the application itself because it uses a different threading model.

[choilive → throw_aw100]

Rails also has an application level connection pool for the database but as I understand a connection pooler (pgbouncer et al) between PG and the application servers is still necessary when horizontally scaling.