Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Our experience using Clojure to speed up Beanstalk

blog.beanstalkapp.com

Post reply on HN
Print view View original

41–50 of 75 posts

Re: Our experience using Clojure to speed up Beanstalk

#41

Post by swannodette »

igouy wrote: post #33
swannodette wrote: post #19

Earlier quoted context omitted.

Alioth benchmarks are out of date as far as Clojure is concerned. These days it's not much work to get Clojure to deliver identical to Java performance. Better versions of the same benchmarks here that show the same performance as Java that you verify yourself - http://github.com/clojure/test.benchmark

>>out of date as far as Clojure is concerned<< What a pity that Clojure programs, written months ago to do benchmarks game tasks, have not been contributed to the benchmarks game for all to see!

All in good time Isaac :)

Re: Our experience using Clojure to speed up Beanstalk

#42

Post by igouy »

swannodette wrote: post #41
igouy wrote: post #33

Earlier quoted context omitted.

>>out of date as far as Clojure is concerned<< What a pity that Clojure programs, written months ago to do benchmarks game tasks, have not been contributed to the benchmarks game for all to see!

All in good time Isaac :)

Let's hope the benchmarks game website is still being updated when that time arrives ;)

Re: Our experience using Clojure to speed up Beanstalk

#43

Post by lrem »

igouy wrote: post #39
lrem wrote: post #37

Earlier quoted context omitted.

Among others: because of completely arbitrary and I'd dare to say weird rules. Programs are not meant to be written in idiomatic language. They are meant to resemble the C implementation. In many cases you can see that the program representing the language in the comparison is neither the fastest nor the simplest of the submissions.

You've made a bunch of claims without showing any evidence to support them. Please point to specific examples we can all look at on the website which show -- "Programs are not meant to be..." -- which show -- "They are meant to resemble the C implementation." etc

I'm not going to back up these claims in any other way than pointing the "interesting alternative" programs that appear in some comparisons, which tend to be faster than the chosen versions. For example here: http://shootout.alioth.debian.org/u64q/benchmark.php?test=fa... Both Lisp and Java alternatives are faster than the "fastest" solution (written in Fortran). Finding any more support for the years-old opinion I voiced seems too much work to be worth it.

Re: Our experience using Clojure to speed up Beanstalk

#45

Post by Rayne »

cmelbye wrote: post #29
dsabanin wrote: post #9

Earlier quoted context omitted.

Have you seen Leiningen[1]? It pretty much solves packaging and deploying problem. Awesome tool. Also if you're into Web development, I can recommend playing with Noir[2] framework and Korma[3] for SQL abstraction. Heroku also support deploying Clojure apps out of the box, so you can easily use a free tier to get something out there. [1] https://github.com/technomancy/leiningen [2] http://webnoir.org/ [3] http://sqlk…

I've got a question about Noir. Is it necessary for me to write HTML with Clojure, or can I separate it and write plain HTML somehow? Writing HTML in the middle of my Clojure code doesn't appeal to me coming from a MVC background...

You can use anything you want for templating. I tend to use Mustache (via the stencil library) for my templating. A lot of people also use Enlive.

Re: Our experience using Clojure to speed up Beanstalk

#50

Post by Uchikoma »

trimbo wrote: post #13

> I’ve been looking for an excuse to use Clojure in a production environment for a while Except in wanting to mess around with Clojure, you didn't use the best tool for the job. The Clojure solution now uses parallel implementations of Git and SVN to solve the problem, rather than the core code of SVN and Git. And now you also have a one-off daemon written in Clojure. It doesn't have the same support structure, ops r…

Not sure how C changed in the last 20 years, but back then, C was a pain to develop, pain to debug, pain to maintain - yes I loved it though.

I'm also not sure I'd compare it to Clojure and suggest it as a better tool for this job.

Post reply on HN