GWT 2.1+ Compiler issues

132 views
Skip to first unread message

Brian

unread,
Jul 11, 2011, 11:00:08 AM7/11/11
to Google Web Toolkit
Hi

I am upgrading my GWT app from 2.0 to 2.3. When I'm compiling with
2.1, 2.2 or 2.3 I am seeing a huge increase in the memory usage. I'm
giving it 3Gb and its maxing this out. Any less than this and I am
getting OutOfMemoryExceptions. I'm also noticing that its writing
massive amounts of data to disk. It is writing gwt88282368723byte-
cache to this directory C:\Users\MyName\AppData\Local\Temp\ . I can
see previous files like this from 2.0 builds that range from 3MB -
10MB in size, but with GWT 2.3 the size of the byte-cache file is now
22GB! This is making my PC really sluggish and its pretty much
unusable while I'm compiling.

I'm wondering of anyone else has come across this with GWT 2.3?

Thanks

Brian

Kevin Jordan

unread,
Jul 11, 2011, 1:22:23 PM7/11/11
to Google Web Toolkit
I've noticed that with GWT 2.3 and RequestFactory stuff added it takes
2x as long to compile now on a quad core AMD machine with 8GB of RAM.

Brian

unread,
Jul 12, 2011, 6:11:12 AM7/12/11
to Google Web Toolkit
Thats interesting. I also have a quad core AMD with 8GB of RAM. Its 64
bit windows running on a Dell Studio XPS 7100.
I wonder if anyone else has experienced this. It just seems really
strange that moving from one version to another would have such an
impact on compilation time.

Ashwin Desikan

unread,
Jul 12, 2011, 8:43:40 AM7/12/11
to google-we...@googlegroups.com, Google Web Toolkit
I have a quad core as well and have experienced slowness. I think it more so to do with validating XML files. I don't believe it has anything to do with requestfactory.

Both validation and context assist are painfully slow.

Thanks
Ashwin

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
>

David Chandler

unread,
Jul 12, 2011, 2:01:39 PM7/12/11
to google-we...@googlegroups.com
Possibly related:



Such a huge jump in memory usage with 2.3 is certainly not typical.

/dmc
--
David Chandler
Developer Programs Engineer, GWT+GAE
w: http://code.google.com/

Jeff Larsen

unread,
Jul 12, 2011, 2:44:01 PM7/12/11
to google-we...@googlegroups.com
I put this in the issue tracker, but I wrote a groovy script to delete every file in the temp directory. Feel free to adapt it to however you need. Change the first line to the correct directory however. 

def directory = "C:\\Documents and Settings\\jlarsen\\Local Settings\\Temp" //CHANGE ME
deleteDirectory(directory)



public void deleteDirectory(String directory){
    File file = new File(directory)
    file.listFiles().each{
        println(it.getName())
        try{
            deleteDirectory(directory+"/"+it.getName())
        }catch(Exception e){
               //Do nothing. If the file is blocked, we don't care. 
        } 
        try{
           it.delete()
        }
           catch(Exception e){
               println(e)
           //do nothing, if we can't delete the file, we don't care. 
        }
    }
}

softmahi

unread,
Jul 12, 2011, 5:57:47 PM7/12/11
to google-we...@googlegroups.com
Hi here whats it stands for ?

Brian

unread,
Jul 13, 2011, 5:40:44 AM7/13/11
to Google Web Toolkit
I'm not using Google Plugin for Eclipse. Its simply compiling GWT with
Maven 2.1 from the command line

Kevin Jordan

unread,
Jul 17, 2011, 4:30:47 PM7/17/11
to Google Web Toolkit
Yeah, I'm not doing it in Eclipse either. I'm doing it in Jenkins
with Maven. Takes anywhere from 20-50 minutes now whereas before I
switched to 2.3 and started adding RequestFactory stuff, it took 6-10
minutes. It also seems to take 11GB of memory which is my all my main
memory + most of the swap partition I've set up.

Kevin Jordan

unread,
Jul 18, 2011, 2:24:18 PM7/18/11
to Google Web Toolkit
Well, I've figured out if I limit the gwt-maven-plugin <localWorkers>
section to 2 in my <configuration> for it, it doesn't hammer the
memory nearly as much as when it defaults to the usual number which is
how many processors/cores you have.
Reply all
Reply to author
Forward
0 new messages