Dev Mode results in 'spinning wheel' delays on Mac

[Eric]

I'm using GWT 2.4 I find that after I launch dev (hosted) mode, which
itself takes around 30 seconds, the first page load comes up fine.
But if I start editing java files and do a browser refresh, I find
that very soon the browser refresh starts 'hanging', and I get the
dreaded spinning wheel pointer icon on the mac. It doesn't matter if
I use Firefox or Safari, after the first few changes the subsequent
browser refresh takes forever to complete.

Do other people experience this problem when using Dev mode? Are
there things I can do/configure to work around this unfortunate
performance problem?

[Rob]

Do other people experience this problem when using Dev mode? 

Yes, I do.  I just found your post searching for "devmode performance".  I wish I knew how to fix it as it makes development painful.  I'm also on a Mac - a new Macbook Pro with 4GB RAM, and it just gets hosed by GWT development.  As you say, the dreaded rainbow wheel of death is everywhere.  Eclipse or IntelliJ starts taking a second to respond to respond to keystrokes.  It's odd because activity monitor (inexact science, I admit) shows low CPU use, and a GB of inactive memory, so what else could it be... disk IO, message passing?

[Shawn Brown]

>> Do other people experience this problem when using Dev mode?

No.

I think you people are both seeing it swap from lack of memory.

What do you have in your dev mode VM args? I have -Xss16M -Xmx1G
What do you have for eclipse.ini?

I have
-XX:MaxPermSize=512m
-Xms40m
-Xmx1G

Neither of these settings may be ideal but they pretty much work for me.
I also watched the heap size in eclipse (show it via eclipse
preferences) and sometimes I restart dev mode when it creeps up too
high and won't go back down.

Shawn

[Rob]

On Saturday, April 7, 2012 12:52:14 AM UTC-4, Shawn wrote:

>> Do other people experience this problem when using Dev mode?

No.

I think you people are both seeing it swap from lack of memory.

What do you have in your dev mode VM args?  I have -Xss16M -Xmx1G

Mine was -Xmx420M, so I will change that and see how it goes.  At first here it seems to be better. I run devmode separately from the IDE so I think the IDE settings will not need changing.

I don't see how it could be swapping, since my OS monitor say there is 1GB of inactive memory.  But perhaps the java process behaves badly when it is on the verge of running out of heap, but not yet producing memory errors.

Rob