I am a Linux user as well and this indeed sounds a bit alarming (but I
haven't tested it on my machine yet, though...) Does somebody has a
bit more information about the reason, current state, etc.?

Thanks!

2009/11/28 David Brown <cloj...@davidb.org>:
> This commit:
>
>     commit 5577a47a390782d7ab911c2e3c4c8be1b0341aa8
>     Author: Rich Hickey <richhic...@gmail.com>
>     Date:   Sat Feb 7 14:46:56 2009 +0000
>
>         added sync to writeClassFile
>
> Adds a 'sync()' call to the class file write.  On systems where the
> underlying fsync() call causes a flush all the way to disk (Linux)
> this makes AOT compilation about an order of magnitude slower,
> especially given the large number of functions in typical clojure
> code.
>
> Anyone know the history behind this?  It makes AOT compilation on
> Linux about 5x slower than on OSX.
>
> The call to sync() takes longer than the compilation did.  It would be
> a win to just clean all of the class files and rebuild after a crash.
>
> The current behavior makes working off of battery on a laptop
> unworkable, since it keeps the harddisk from spinning down.
>
> These are just the output of the compiler, easily regenerated.
>
> David
>
> --
> 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 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

Reply via email to