I'm not really familiar with all of the choices you listed, but of the ones that I do know, I don't really consider Dropwizarr or Finagle as alternatives to a web framework like Django (neither is Jersey, but that's already a component of Dropwizard).
But for many applications, the necessary framework pieces are there in many of the frameworks I listed: routing, database connection pooling, ORM, sessions, cookie support, form validation, JSON serialization, server-side templates, XSS/CSRF countermeasures, email, REST clients, authentication, etc. or some mix thereof. For example, Dropwizard provides a majority of those pieces.
Also agreed that you can write low-performance code on anything, and you're right there are several JVM libraries that perform poorly. But the JVM gives a very high "high water mark," so to speak. As do Go, Haskell, Lua, Erlang, and other platforms.
However, would you attempt to build a traditional multi-page web application (what Django is really built for) in Dropwizard? Is anyone doing that? I'd love to see some examples and patterns for doing that.
Surely the absence of a SSD and hardware vs virtual hosting is more likely to affect Postgres than Node? Node presumably runs all in memory and is more likely to be CPU bound (or waiting) than disk IO bound.