On Wednesday, June 24, 2015 at 4:03:39 PM UTC-4, Mike Grabowski wrote: > > Thanks for the reference, I've seen it before and it looks interesting, > especially thanks to the failover built-in. It also greatly shows how > Clojure can reduce the `Java boilerplate`. > > Speaking on the performance note, I am not entirely sure what's causing my > REST API to be slower than `Node.js` one, I have two the same auth logic > implemented in both Node/Clojure. The Node.js version is running on Heroku > (London) with MongoLab hosted in (US-east-1) which can handle login in > 140ms. On the other hand, the Clojure Aleph/Compojure hosted in London on > DigitalOcean with MongoHQ database hosted in the same DigitalOcean region > handles the same thing in 350ms in the best case. This is really weird as > the `non-database` request is 40ms faster than Node.js one. I need to > investigate, but apart from that, all good so far. >
350ms sounds fast enough for a low-frequency user interaction. In fact, once login is fast enough not to annoy your users, you don't *want* any more speed from it, as further speedup then only benefits blackhats trying to brute-force one of your users' accounts. So, it might be a feature, not a bug. -- 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.
