Also note that Compojure (and Ring) applications are artificially limiting, because they cannot utilize the containers' full capabilities (Ring apps can't go async at the container level, they can't use NIO responses, etc).
For these use-cases, you'll have to program directly to container itself, use Pedestal (limiting to the Servlet-only case), or use Aleph (rides on top of Netty). I'd also encourage you to reconsider your benchmark - ask yourself, "What does this really tell me?" Is the benchmark an accurate representation of the kinds of HTTP services you build? Are the payloads (parsing and generation) representative of common data you deal with in the systems you build? Is the network, topology, and traffic generation realistic (or at least analogous) to production systems? Can the results of the benchmark directly inform architectural considerations of real systems? Food for thought! Good luck! Cheers, Paul -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
