Hi All,
I even tried upgrade of GWT 2.5 and SuperDevMode.
But Still no improvement.
Thanks.
On Tuesday, 4 September 2012 11:40:19 UTC+5:30, Niraj Salot wrote:
Hi Members,
We are using GWT Version 2.4 in our current project. On server side, we
are using Spring Custom JDBC framework.
We
On Friday, September 7, 2012 9:06:51 AM UTC+2, Niraj Salot wrote:
Hi All,
I even tried upgrade of GWT 2.5 and SuperDevMode.
But Still no improvement.
Really?! You mean that each time you hit the DevMode On bookmarklet and
Compile button, it takes 4-6 minutes before the page is refreshed
Maybe you should get more RAM...4GB isn't a lot when running all the things you
need for GWT development. Alternatively, run some (or even all) of the required
processes on another computer.
Paul
On 06/09/12 05:33, Niraj Salot wrote:
Hi Members,
Thanks for all your suggestion/comments.
We
I don't know if I am missing something, but, have you tried to upgrade to
GWT 2.5 and use SuperDevMode? In my case I was needing 2 minutes each time
that I made any change and now 15 seconds(or less).
Maybe for your developers is worth to try it.
My 2 cents,
Adolfo.
2012/9/6 Paul Robinson
Niraj: IMHO if you want to agile GWT development you want to develop using
the GWT devel mode or the GWT2.5 SuperDevMode (haven't tried myself)
instead modify java - compile with ant - see the changes. You could
ignore devel mode vs production differences when hard - developing, and
perform a
Instead of compiling one permutation at a time, there is an option to
compile multiple permutations at the same time by mutli-process.
Here is the parameter I used in the Ant build.xml file (sorry, I don't use
maven), all you needed to add -localWorkers within gwtc target tag:
target name=gwtc
Have you considered using a SSD instead of a HD?
I've cut my compile times dramatically that way.
On Thu, Sep 6, 2012 at 12:08 PM, Chak Lai chaklam@gmail.com wrote:
Instead of compiling one permutation at a time, there is an option to
compile multiple permutations at the same time by
Oh, and if you have to use an external device, use esata rather than usb.
while usb has higher burst speeds, esata has much higher sustained
transfer speeds.
On Thu, Sep 6, 2012 at 3:35 PM, Andy Stevko andy.ste...@gmail.com wrote:
Have you considered using a SSD instead of a HD?
I've cut my
Niraj, you didn't mention the -localWorkers flag. On a quad-core
machine that reduced our compile time to about 1/3 of what it was (our 300s
compile time became 100s).
Ryan
On Tuesday, September 4, 2012 1:10:19 AM UTC-5, Niraj Salot wrote:
Hi Members,
We are using GWT Version 2.4 in our
Be happy that its only 4-6 minutes :)) You can't really speed it up because
at the end the amount of source you need to compile to JS is always the
same.
But you can use a distributed build which could reduce the compilation time
to the time of a single permutation if you have enough hosts to
Hi Members,
Thanks for all your suggestion/comments.
We have already tried below mentioned options to improve the compilation
time overall.
1. Memory Settings. -Xmx and Xms
2. localWorkers
3. DraftCompile
The question could arise to members mind that why we need to compile a lot
Hi Members,
We are using GWT Version 2.4 in our current project. On server side, we are
using Spring Custom JDBC framework.
We are using Maven as our Build Tool. The application is getting deployed
on JBOSS 7 Server.
Currently we have everything in one single Eclipse Project. Means one
On 3 September 2012 23:10, Niraj Salot salotni...@gmail.com wrote:
1) Will this help us in Improving the compilation time?
No.
2) IF we change only Module 2 and then compile Module Main, will GWT still
compile Module 1 as it is inherited by Module Main?
Yes.
Please share your views on
On Tuesday, September 4, 2012 9:04:05 AM UTC+2, Hilco Wijbenga wrote:
On 3 September 2012 23:10, Niraj Salot salot...@gmail.com javascript:
wrote:
1) Will this help us in Improving the compilation time?
No.
2) IF we change only Module 2 and then compile Module Main, will GWT
Another possibility would be to replace some classes with stubs (-
dependency injection) - only activating the functionality that is currently
interesting. The rest doesn't need to be compiled. Of course it depends on
the application's architecture, if this can be done easily or not.
On
What could possibly help is to precompile the modules into *.gwtar files,
but it's something that's supposed to only be used by GWT itself (you'll
find such gwtar files in the gwt-user.jar) AFAIK. At least it's not
designed to build libraries, as the gwtar files depend on the version of
You could also move the compilation process to a bigger machine on the
cloud and then if you need to run the compiled site locally do a script to
download the content. That improved a lot the compilation time for me.
You can also try doing distributed builds (I personally never tried), but
here
17 matches
Mail list logo
