@bascule so yeah, i changed one const in the go stdlib, and smashed that java benchmark to death, as it should be
@raggi master/slave read/write split or pooling or load balancing via JDBC is awesome but the fault tolerance might incur a performance hit
-
-
@bascule nod. i suspect for this rudimentary use case, these two systems are relatively indistinguishable, except for ram vs features -
@raggi JVM will always lose at RAM and startup time, but optimizes for amortized time -
@bascule well, the bench in question also compares an unframework toolkit to a raw stdlib setup. seems pitched against java anyway -
@raggi that said if you optimize for RAM or startup time Go wins!!! -
@bascule or if you want to work without a web framework, it seems. after my patch at least. -
@raggi raw Netty? -
@bascule might have to be, to make the test fair. drop wizard isn't a tall stack, but something in there may be to blame
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.