Yehuda Katz wrote: > This is actually a combination of expensive mtime and an errant GC.start > in the reloading thread that happens on every iteration. On MRI, > GC.start is innocuous, but in JRuby it's expensive as hell. > > The reason that Rails doesn't use CPU is that it reloads all files on > every request, so it doesn't need to watch for changes. This is so > expensive that a plugin called dev_mode_performance exists for Rails > that changes Rails' behavior so that it *does* poll. > > We'll be removing the errant GC.start in 1.0.4 (to be released Monday) > and then we can take another look at how to speed up the devmode thread.
How much did removing GC.start improve things? I remember you mentioned on IRC, but I have forgotten. - Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
