On 28/08/2010, at 11:06 PM, Marc Guenther wrote:
> Hi,
>
> Is anyone else using JRebel successfully? I am currently playing around with it, and I notice that it makes app startup and usage very slow.
>
> App startup changed from 9sec to 63sec. I think I _could_ live with that, but every click is now also very slow, at least for new pages. What usually takes 2secs (for a slow page) now easily takes 20s.
While I do notice a slow down, I don't notice anything of this magnitude. Do you have a massive classpath that causes a huge number of classes to be loaded on "slow pages"?
> This only happens on new pages, though, clicks to pages that have been used already are as fast as ever (so once I am where I need to be in my app, its fast, and it works quite nicely).
>
> So I suspect it is something to do with the classloader, and jrebel instrumenting all new classes, or whatever it does. I checked with -Drebel.log=true that it is only instrumenting our own classes, and not the whole of Webobjects. The output of -Drebel.log.perf=true doesn't really tell me anything.
It may be best to contact zeroturnaround directly about this so that they can look at issue. I have dealt with them directly on several occasions and they have been very helpful. JR does make classloading slower, and adds a small overhead to runtime execution, but unless your are loading a lot of classes it shouldn't be unusably slow.
> I'm using the most recent jrebel 3.1.2a. I'm on MacOSX 10.6, Java 1.5, Eclipse 3.6 and WOLips 3.6.6116, using WO 5.4.3 (no Wonder)
How exactly are you using 1.5 on OSX 10.6? It only ships with and supports 1.6.
> Is this a problem with my setup, or is it so slow for everybody?
Is this issue limited to the one application? In general it shouldn't be that slow unless your application is huge.
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10)
This archive was generated by hypermail 2.0.0 : Sat Aug 28 2010 - 22:00:34 UTC