ANN: Grails 2.1 Released!
Locked
123
123
ANN: Grails 2.1 Released!
 
Administrator
|
Hi all,
We are pleased to announce the final release of Grails 2.1! Grails 2.1 can be downloaded from the usual place at: http://grails.org/Download This release includes several new features and improvements since the 2.0 release, including: * Improved Maven Support including multi-module builds * An official caching solution via the new cache plugin (see http://grails.org/plugin/cache) * A new wrapper feature for building Grails applications without requiring a Grails install For more information on these features please see the What's new guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 We now are focusing on the 2.2 release which will include: * Groovy 2.0 * Forked execution of run-app * Namespace support The development time for 2.2 will be pretty short as we want to get Groovy 2.0 in the hands of Grails developers as soon as possible so expect a milestone in the next few weeks. Enjoy! -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
Congrats :)
2012/7/5 Graeme Rocher <[hidden email]> Hi all, |
|
In reply to this post by Graeme Rocher-4
Cheers to another release :)
On Thu, Jul 5, 2012 at 7:10 PM, Graeme Rocher <[hidden email]> wrote: Hi all, Thanks and regards, Ravi Teja |
|
CONTENTS DELETED
The author has deleted this message.
|
RE: ANN: Grails 2.1 Released!
|
In reply to this post by Graeme Rocher-4
Great work team, exciting stuff! I love the shorter more frequent release cycle personally, so new features are in the hands of developers sooner than later.
Ryan ________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Graeme Rocher [[hidden email]] Sent: Thursday, July 05, 2012 8:40 AM To: user Subject: [grails-user] ANN: Grails 2.1 Released! Hi all, We are pleased to announce the final release of Grails 2.1! Grails 2.1 can be downloaded from the usual place at: http://grails.org/Download This release includes several new features and improvements since the 2.0 release, including: * Improved Maven Support including multi-module builds * An official caching solution via the new cache plugin (see http://grails.org/plugin/cache) * A new wrapper feature for building Grails applications without requiring a Grails install For more information on these features please see the What's new guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 We now are focusing on the 2.2 release which will include: * Groovy 2.0 * Forked execution of run-app * Namespace support The development time for 2.2 will be pretty short as we want to get Groovy 2.0 in the hands of Grails developers as soon as possible so expect a milestone in the next few weeks. Enjoy! -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
Good to hear - will give it a spin to see about its stability. Not to be the negative guy around here but the 2.0 release of Grails has made me cautious... Groovy 2.0 didn't do very good either in terms of regression...
Anyways - keep up the good work! M.
2012/7/5 Ryan Vanderwerf <[hidden email]> Great work team, exciting stuff! I love the shorter more frequent release cycle personally, so new features are in the hands of developers sooner than later. |
|
Don't get me wrong, I'm a grails enthusiast, but I have to agree with Matthias on this. The 2.0 release got me quite concerned with regression, and even more concerned with memory usage. Grails 1.3.7 used 500mb of memory, grails 2.0 uses a minimum of 700mb, which seems a pretty high mem consumption to me... On Jul 5, 2012 11:51 AM, "Matthias Hryniszak" <[hidden email]> wrote:
Good to hear - will give it a spin to see about its stability. Not to be the negative guy around here but the 2.0 release of Grails has made me cautious... Groovy 2.0 didn't do very good either in terms of regression... |
Re: ANN: Grails 2.1 Released!
|
On Thu, Jul 5, 2012 at 4:59 PM, Felipe Carvalho <[hidden email]> wrote:
I've got the same reservations, but will likely be a guinea pig on this one, as 2.1 has GORM code that I've been back-patching into 2.0.x releases, and I'm looking forward to being able to stop doing that. I'm waiting until I see complete support from STS, though, as STS integration was something of a regression disaster with 2.0.1. Please announce when STS supports grails 2.1 directly and I'll be first in line to get going on 2.1.
--sam |
|
running 2.1.0 project just upgraded from 2.0.4 with ggts 3.0.0.m2
without problems... ofc ggts still lacks a "real" support of the interactive shell but since a run-app with the springloaded agent enabled seems to load changes from a 2nd process fine, starting the app via a run-app launch config and then using the in-built command prompt is ok for me. -------- Original Message -------- Subject: Re: [grails-user] ANN: Grails 2.1 Released! From: Samuel Gendler <[hidden email]> To: [hidden email] Date: Thu, 5 Jul 2012 18:41:40 -0700 > > > On Thu, Jul 5, 2012 at 4:59 PM, Felipe Carvalho > <[hidden email] <mailto:[hidden email]>> wrote: > > Don't get me wrong, I'm a grails enthusiast, but I have to agree > with Matthias on this. The 2.0 release got me quite concerned with > regression, and even more concerned with memory usage. Grails 1.3.7 > used 500mb of memory, grails 2.0 uses a minimum of 700mb, which > seems a pretty high mem consumption to me... > > > I've got the same reservations, but will likely be a guinea pig on this > one, as 2.1 has GORM code that I've been back-patching into 2.0.x > releases, and I'm looking forward to being able to stop doing that. I'm > waiting until I see complete support from STS, though, as STS > integration was something of a regression disaster with 2.0.1. Please > announce when STS supports grails 2.1 directly and I'll be first in line > to get going on 2.1. > > --sam > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
Administrator
|
In reply to this post by felipecao
There were several changes made that were breaking changes (especially
around unit tests) and for that I understand the upgrade task has become bigger. May I suggest someone create a JIRA issue called "Can't upgraded from 1.3.x" with subtasks for each problem upgrading and maybe we can improve the upgrade experience by targeting issues that are particularly problematic for upgrading. We want people to upgrade as the 1.3.x line is not being developed anymore Cheers On Fri, Jul 6, 2012 at 1:59 AM, Felipe Carvalho <[hidden email]> wrote: > Don't get me wrong, I'm a grails enthusiast, but I have to agree with > Matthias on this. The 2.0 release got me quite concerned with regression, > and even more concerned with memory usage. Grails 1.3.7 used 500mb of > memory, grails 2.0 uses a minimum of 700mb, which seems a pretty high mem > consumption to me... > > On Jul 5, 2012 11:51 AM, "Matthias Hryniszak" <[hidden email]> wrote: >> >> Good to hear - will give it a spin to see about its stability. Not to be >> the negative guy around here but the 2.0 release of Grails has made me >> cautious... Groovy 2.0 didn't do very good either in terms of regression... >> >> Anyways - keep up the good work! >> >> M. >> >> 2012/7/5 Ryan Vanderwerf <[hidden email]> >>> >>> Great work team, exciting stuff! I love the shorter more frequent release >>> cycle personally, so new features are in the hands of developers sooner than >>> later. >>> >>> Ryan >>> ________________________________________ >>> From: [hidden email] [[hidden email]] On Behalf Of >>> Graeme Rocher [[hidden email]] >>> Sent: Thursday, July 05, 2012 8:40 AM >>> To: user >>> Subject: [grails-user] ANN: Grails 2.1 Released! >>> >>> Hi all, >>> >>> We are pleased to announce the final release of Grails 2.1! Grails 2.1 >>> can be downloaded from the usual place at: >>> >>> http://grails.org/Download >>> >>> This release includes several new features and improvements since the >>> 2.0 release, including: >>> >>> * Improved Maven Support including multi-module builds >>> * An official caching solution via the new cache plugin (see >>> http://grails.org/plugin/cache) >>> * A new wrapper feature for building Grails applications without >>> requiring a Grails install >>> >>> For more information on these features please see the What's new >>> guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 >>> >>> We now are focusing on the 2.2 release which will include: >>> >>> * Groovy 2.0 >>> * Forked execution of run-app >>> * Namespace support >>> >>> The development time for 2.2 will be pretty short as we want to get >>> Groovy 2.0 in the hands of Grails developers as soon as possible so >>> expect a milestone in the next few weeks. >>> >>> Enjoy! >>> >>> -- >>> Graeme Rocher >>> Grails Project Lead >>> SpringSource - A Division of VMware >>> http://www.springsource.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> > -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
What about memory, consumption?
I can understad memory is cheap these days but jumping from 500MB to 1GB (my experience YMMV and this is only development) to me can only be an indicator that something is fundamentally messed up. I would at least like to know why this big of a jump happened? Cheers, Alex. On Fri, Jul 6, 2012 at 9:11 AM, Graeme Rocher <[hidden email]> wrote: > There were several changes made that were breaking changes (especially > around unit tests) and for that I understand the upgrade task has > become bigger. > > May I suggest someone create a JIRA issue called "Can't upgraded from > 1.3.x" with subtasks for each problem upgrading and maybe we can > improve the upgrade experience by targeting issues that are > particularly problematic for upgrading. We want people to upgrade as > the 1.3.x line is not being developed anymore > > Cheers > > On Fri, Jul 6, 2012 at 1:59 AM, Felipe Carvalho > <[hidden email]> wrote: >> Don't get me wrong, I'm a grails enthusiast, but I have to agree with >> Matthias on this. The 2.0 release got me quite concerned with regression, >> and even more concerned with memory usage. Grails 1.3.7 used 500mb of >> memory, grails 2.0 uses a minimum of 700mb, which seems a pretty high mem >> consumption to me... >> >> On Jul 5, 2012 11:51 AM, "Matthias Hryniszak" <[hidden email]> wrote: >>> >>> Good to hear - will give it a spin to see about its stability. Not to be >>> the negative guy around here but the 2.0 release of Grails has made me >>> cautious... Groovy 2.0 didn't do very good either in terms of regression... >>> >>> Anyways - keep up the good work! >>> >>> M. >>> >>> 2012/7/5 Ryan Vanderwerf <[hidden email]> >>>> >>>> Great work team, exciting stuff! I love the shorter more frequent release >>>> cycle personally, so new features are in the hands of developers sooner than >>>> later. >>>> >>>> Ryan >>>> ________________________________________ >>>> From: [hidden email] [[hidden email]] On Behalf Of >>>> Graeme Rocher [[hidden email]] >>>> Sent: Thursday, July 05, 2012 8:40 AM >>>> To: user >>>> Subject: [grails-user] ANN: Grails 2.1 Released! >>>> >>>> Hi all, >>>> >>>> We are pleased to announce the final release of Grails 2.1! Grails 2.1 >>>> can be downloaded from the usual place at: >>>> >>>> http://grails.org/Download >>>> >>>> This release includes several new features and improvements since the >>>> 2.0 release, including: >>>> >>>> * Improved Maven Support including multi-module builds >>>> * An official caching solution via the new cache plugin (see >>>> http://grails.org/plugin/cache) >>>> * A new wrapper feature for building Grails applications without >>>> requiring a Grails install >>>> >>>> For more information on these features please see the What's new >>>> guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 >>>> >>>> We now are focusing on the 2.2 release which will include: >>>> >>>> * Groovy 2.0 >>>> * Forked execution of run-app >>>> * Namespace support >>>> >>>> The development time for 2.2 will be pretty short as we want to get >>>> Groovy 2.0 in the hands of Grails developers as soon as possible so >>>> expect a milestone in the next few weeks. >>>> >>>> Enjoy! >>>> >>>> -- >>>> Graeme Rocher >>>> Grails Project Lead >>>> SpringSource - A Division of VMware >>>> http://www.springsource.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >> > > > > -- > Graeme Rocher > Grails Project Lead > SpringSource - A Division of VMware > http://www.springsource.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
|
Hi all, 1.3.9 vs 2.1.0 vs JBoss 7.1.1 vs RoR 3.2.6 Startup time: 15s 32s 2.2s 3s Memory consumption: 358MB 571MB 117MB 36.1MB Apart of memory consumption I'm really worried about the startup time. I know that one should do that just once with the new agent for reloading classes but it is obvious that it's not what is going to happen in situations like when you modify the domain (just to point out the obvious). I know it's kind of a Java thing to start slowly and Groovy isn't doing very well to speed things up (rather the opposite). But can't we instead of adding features work on stability and performance for a change? I mean I understand the demand for installation-less, maven-based Grails projects but what good are they for if the "grails run-app" command starts 15 times slower than JBoss 7.1.1 and takes up 5 times more memory (and with JRebel Social you do get class reloading for free)... Like I said: I don't want to be the negative guy here but starting with the 2.0 release the "productivity" thing that Grails is so big about isn't going to make for a strong defense anymore with the parameters described above. Best regards, Matthias.
2012/7/6 Alex Shneyderman <[hidden email]> What about memory, consumption? |
Re: ANN: Grails 2.1 Released!
|
|
In reply to this post by zyro
@zyro vote up here :)
https://issuetracker.springsource.com/browse/STS-2171
2012/7/6 zyro <[hidden email]> running 2.1.0 project just upgraded from 2.0.4 with ggts 3.0.0.m2 |
Re: ANN: Grails 2.1 Released!
|
Thanks a lot. Congrats!
--- Sébastien Arbogast http://sebastien-arbogast.com 2012/7/6 Konstantinos Kostarellis <[hidden email]>: > @zyro vote up here :) > > https://issuetracker.springsource.com/browse/STS-2171 > > > 2012/7/6 zyro <[hidden email]> >> >> running 2.1.0 project just upgraded from 2.0.4 with ggts 3.0.0.m2 >> without problems... >> >> ofc ggts still lacks a "real" support of the interactive shell but since >> a run-app with the springloaded agent enabled seems to load changes from >> a 2nd process fine, starting the app via a run-app launch config and >> then using the in-built command prompt is ok for me. >> >> -------- Original Message -------- >> Subject: Re: [grails-user] ANN: Grails 2.1 Released! >> From: Samuel Gendler <[hidden email]> >> To: [hidden email] >> Date: Thu, 5 Jul 2012 18:41:40 -0700 >> >> > >> > >> > On Thu, Jul 5, 2012 at 4:59 PM, Felipe Carvalho >> > <[hidden email] <mailto:[hidden email]>> wrote: >> > >> > Don't get me wrong, I'm a grails enthusiast, but I have to agree >> > with Matthias on this. The 2.0 release got me quite concerned with >> > regression, and even more concerned with memory usage. Grails 1.3.7 >> > used 500mb of memory, grails 2.0 uses a minimum of 700mb, which >> > seems a pretty high mem consumption to me... >> > >> > >> > I've got the same reservations, but will likely be a guinea pig on this >> > one, as 2.1 has GORM code that I've been back-patching into 2.0.x >> > releases, and I'm looking forward to being able to stop doing that. I'm >> > waiting until I see complete support from STS, though, as STS >> > integration was something of a regression disaster with 2.0.1. Please >> > announce when STS supports grails 2.1 directly and I'll be first in line >> > to get going on 2.1. >> > >> > --sam >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
Administrator
|
In reply to this post by Matthias Hryniszak
You're talking Apples and Oranges here, you cannot compare starting up
a container with no actual application deployed to what Grails is doing. You would need to compare the time taken to a) build a war file with maven/ant etc. b) deploy it to JBoss c) startup JBoss Calculate the times to do those 3 things and then do a Grails vs JBoss comparison. As for RoR well that is what you get with a full interpreted language and no virtual machine. In terms of the difference between 1.3.x and 2.0.x in memory consumption and startup, this is pretty much all the reloading agent. For 2.2 I'm working on a forked run-app implementation that doesn't place the agent on the system classpath. This should speed things up, although at the cost of forking the JVM. I'm also working on optimizing various parts of the build system, a lot of this refactoring / optimization has already been done. I hope we can realize an improvement with 2.2. Otherwise we can always add back the ability to disable the reloading agent have class loader based reloading for those who prefer speed over reloading consistency Cheers On Fri, Jul 6, 2012 at 10:38 AM, Matthias Hryniszak <[hidden email]> wrote: > Hi all, > > 1.3.9 vs 2.1.0 vs JBoss 7.1.1 vs RoR 3.2.6 > > Startup time: > > 15s > 32s > 2.2s > 3s > > Memory consumption: > > 358MB > 571MB > 117MB > 36.1MB > > (all figures from the 3rd start where everything is already downloaded, > compiled, etc. and with the default settings; Oracle Java 1.6.0_32, Ubuntu > 12.04 64bit) > > Apart of memory consumption I'm really worried about the startup time. I > know that one should do that just once with the new agent for reloading > classes but it is obvious that it's not what is going to happen in > situations like when you modify the domain (just to point out the obvious). > > I know it's kind of a Java thing to start slowly and Groovy isn't doing very > well to speed things up (rather the opposite). But can't we instead of > adding features work on stability and performance for a change? I mean I > understand the demand for installation-less, maven-based Grails projects but > what good are they for if the "grails run-app" command starts 15 times > slower than JBoss 7.1.1 and takes up 5 times more memory (and with JRebel > Social you do get class reloading for free)... > > Like I said: I don't want to be the negative guy here but starting with the > 2.0 release the "productivity" thing that Grails is so big about isn't going > to make for a strong defense anymore with the parameters described above. > > > Best regards, > Matthias. > > > 2012/7/6 Alex Shneyderman <[hidden email]> >> >> What about memory, consumption? >> >> I can understad memory is cheap these days but jumping from 500MB to 1GB >> (my experience YMMV and this is only development) to me can only be an >> indicator that something is fundamentally messed up. I would at least like >> to >> know why this big of a jump happened? >> >> Cheers, >> Alex. >> >> On Fri, Jul 6, 2012 at 9:11 AM, Graeme Rocher <[hidden email]> wrote: >> > There were several changes made that were breaking changes (especially >> > around unit tests) and for that I understand the upgrade task has >> > become bigger. >> > >> > May I suggest someone create a JIRA issue called "Can't upgraded from >> > 1.3.x" with subtasks for each problem upgrading and maybe we can >> > improve the upgrade experience by targeting issues that are >> > particularly problematic for upgrading. We want people to upgrade as >> > the 1.3.x line is not being developed anymore >> > >> > Cheers >> > >> > On Fri, Jul 6, 2012 at 1:59 AM, Felipe Carvalho >> > <[hidden email]> wrote: >> >> Don't get me wrong, I'm a grails enthusiast, but I have to agree with >> >> Matthias on this. The 2.0 release got me quite concerned with >> >> regression, >> >> and even more concerned with memory usage. Grails 1.3.7 used 500mb of >> >> memory, grails 2.0 uses a minimum of 700mb, which seems a pretty high >> >> mem >> >> consumption to me... >> >> >> >> On Jul 5, 2012 11:51 AM, "Matthias Hryniszak" <[hidden email]> wrote: >> >>> >> >>> Good to hear - will give it a spin to see about its stability. Not to >> >>> be >> >>> the negative guy around here but the 2.0 release of Grails has made me >> >>> cautious... Groovy 2.0 didn't do very good either in terms of >> >>> regression... >> >>> >> >>> Anyways - keep up the good work! >> >>> >> >>> M. >> >>> >> >>> 2012/7/5 Ryan Vanderwerf <[hidden email]> >> >>>> >> >>>> Great work team, exciting stuff! I love the shorter more frequent >> >>>> release >> >>>> cycle personally, so new features are in the hands of developers >> >>>> sooner than >> >>>> later. >> >>>> >> >>>> Ryan >> >>>> ________________________________________ >> >>>> From: [hidden email] [[hidden email]] On Behalf Of >> >>>> Graeme Rocher [[hidden email]] >> >>>> Sent: Thursday, July 05, 2012 8:40 AM >> >>>> To: user >> >>>> Subject: [grails-user] ANN: Grails 2.1 Released! >> >>>> >> >>>> Hi all, >> >>>> >> >>>> We are pleased to announce the final release of Grails 2.1! Grails >> >>>> 2.1 >> >>>> can be downloaded from the usual place at: >> >>>> >> >>>> http://grails.org/Download >> >>>> >> >>>> This release includes several new features and improvements since the >> >>>> 2.0 release, including: >> >>>> >> >>>> * Improved Maven Support including multi-module builds >> >>>> * An official caching solution via the new cache plugin (see >> >>>> http://grails.org/plugin/cache) >> >>>> * A new wrapper feature for building Grails applications without >> >>>> requiring a Grails install >> >>>> >> >>>> For more information on these features please see the What's new >> >>>> guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 >> >>>> >> >>>> We now are focusing on the 2.2 release which will include: >> >>>> >> >>>> * Groovy 2.0 >> >>>> * Forked execution of run-app >> >>>> * Namespace support >> >>>> >> >>>> The development time for 2.2 will be pretty short as we want to get >> >>>> Groovy 2.0 in the hands of Grails developers as soon as possible so >> >>>> expect a milestone in the next few weeks. >> >>>> >> >>>> Enjoy! >> >>>> >> >>>> -- >> >>>> Graeme Rocher >> >>>> Grails Project Lead >> >>>> SpringSource - A Division of VMware >> >>>> http://www.springsource.com >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe from this list, please visit: >> >>>> >> >>>> http://xircles.codehaus.org/manage_email >> >>>> >> >>>> >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe from this list, please visit: >> >>>> >> >>>> http://xircles.codehaus.org/manage_email >> >>>> >> >>>> >> >>> >> >> >> > >> > >> > >> > -- >> > Graeme Rocher >> > Grails Project Lead >> > SpringSource - A Division of VMware >> > http://www.springsource.com >> > >> > --------------------------------------------------------------------- >> > To unsubscribe from this list, please visit: >> > >> > http://xircles.codehaus.org/manage_email >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
In reply to this post by a.shneyderman
2012/7/6 Alex Shneyderman
> What about memory, consumption? > > I can understad memory is cheap these days but jumping from 500MB to 1GB > (my experience YMMV and this is only development) to me can only be an > indicator that something is fundamentally messed up. I would at least like to > know why this big of a jump happened? I think it's an indicator of well-executed priority allocation of developer time. John --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
Administrator
|
In reply to this post by Graeme Rocher-4
And PS we were of course aware of the increase in startup time due to
the agent for 2.0 hence why we introduced interactive mode which lets you quickly start and stop the application if need be and run commands. If you are a 1.3.x user and haven't tried it I suggest you do so :-) Cheers On Fri, Jul 6, 2012 at 11:58 AM, Graeme Rocher <[hidden email]> wrote: > You're talking Apples and Oranges here, you cannot compare starting up > a container with no actual application deployed to what Grails is > doing. You would need to compare the time taken to > > a) build a war file with maven/ant etc. > b) deploy it to JBoss > c) startup JBoss > > Calculate the times to do those 3 things and then do a Grails vs JBoss > comparison. > > As for RoR well that is what you get with a full interpreted language > and no virtual machine. > > In terms of the difference between 1.3.x and 2.0.x in memory > consumption and startup, this is pretty much all the reloading agent. > For 2.2 I'm working on a forked run-app implementation that doesn't > place the agent on the system classpath. This should speed things up, > although at the cost of forking the JVM. I'm also working on > optimizing various parts of the build system, a lot of this > refactoring / optimization has already been done. I hope we can > realize an improvement with 2.2. > > Otherwise we can always add back the ability to disable the reloading > agent have class loader based reloading for those who prefer speed > over reloading consistency > > Cheers > > On Fri, Jul 6, 2012 at 10:38 AM, Matthias Hryniszak <[hidden email]> wrote: >> Hi all, >> >> 1.3.9 vs 2.1.0 vs JBoss 7.1.1 vs RoR 3.2.6 >> >> Startup time: >> >> 15s >> 32s >> 2.2s >> 3s >> >> Memory consumption: >> >> 358MB >> 571MB >> 117MB >> 36.1MB >> >> (all figures from the 3rd start where everything is already downloaded, >> compiled, etc. and with the default settings; Oracle Java 1.6.0_32, Ubuntu >> 12.04 64bit) >> >> Apart of memory consumption I'm really worried about the startup time. I >> know that one should do that just once with the new agent for reloading >> classes but it is obvious that it's not what is going to happen in >> situations like when you modify the domain (just to point out the obvious). >> >> I know it's kind of a Java thing to start slowly and Groovy isn't doing very >> well to speed things up (rather the opposite). But can't we instead of >> adding features work on stability and performance for a change? I mean I >> understand the demand for installation-less, maven-based Grails projects but >> what good are they for if the "grails run-app" command starts 15 times >> slower than JBoss 7.1.1 and takes up 5 times more memory (and with JRebel >> Social you do get class reloading for free)... >> >> Like I said: I don't want to be the negative guy here but starting with the >> 2.0 release the "productivity" thing that Grails is so big about isn't going >> to make for a strong defense anymore with the parameters described above. >> >> >> Best regards, >> Matthias. >> >> >> 2012/7/6 Alex Shneyderman <[hidden email]> >>> >>> What about memory, consumption? >>> >>> I can understad memory is cheap these days but jumping from 500MB to 1GB >>> (my experience YMMV and this is only development) to me can only be an >>> indicator that something is fundamentally messed up. I would at least like >>> to >>> know why this big of a jump happened? >>> >>> Cheers, >>> Alex. >>> >>> On Fri, Jul 6, 2012 at 9:11 AM, Graeme Rocher <[hidden email]> wrote: >>> > There were several changes made that were breaking changes (especially >>> > around unit tests) and for that I understand the upgrade task has >>> > become bigger. >>> > >>> > May I suggest someone create a JIRA issue called "Can't upgraded from >>> > 1.3.x" with subtasks for each problem upgrading and maybe we can >>> > improve the upgrade experience by targeting issues that are >>> > particularly problematic for upgrading. We want people to upgrade as >>> > the 1.3.x line is not being developed anymore >>> > >>> > Cheers >>> > >>> > On Fri, Jul 6, 2012 at 1:59 AM, Felipe Carvalho >>> > <[hidden email]> wrote: >>> >> Don't get me wrong, I'm a grails enthusiast, but I have to agree with >>> >> Matthias on this. The 2.0 release got me quite concerned with >>> >> regression, >>> >> and even more concerned with memory usage. Grails 1.3.7 used 500mb of >>> >> memory, grails 2.0 uses a minimum of 700mb, which seems a pretty high >>> >> mem >>> >> consumption to me... >>> >> >>> >> On Jul 5, 2012 11:51 AM, "Matthias Hryniszak" <[hidden email]> wrote: >>> >>> >>> >>> Good to hear - will give it a spin to see about its stability. Not to >>> >>> be >>> >>> the negative guy around here but the 2.0 release of Grails has made me >>> >>> cautious... Groovy 2.0 didn't do very good either in terms of >>> >>> regression... >>> >>> >>> >>> Anyways - keep up the good work! >>> >>> >>> >>> M. >>> >>> >>> >>> 2012/7/5 Ryan Vanderwerf <[hidden email]> >>> >>>> >>> >>>> Great work team, exciting stuff! I love the shorter more frequent >>> >>>> release >>> >>>> cycle personally, so new features are in the hands of developers >>> >>>> sooner than >>> >>>> later. >>> >>>> >>> >>>> Ryan >>> >>>> ________________________________________ >>> >>>> From: [hidden email] [[hidden email]] On Behalf Of >>> >>>> Graeme Rocher [[hidden email]] >>> >>>> Sent: Thursday, July 05, 2012 8:40 AM >>> >>>> To: user >>> >>>> Subject: [grails-user] ANN: Grails 2.1 Released! >>> >>>> >>> >>>> Hi all, >>> >>>> >>> >>>> We are pleased to announce the final release of Grails 2.1! Grails >>> >>>> 2.1 >>> >>>> can be downloaded from the usual place at: >>> >>>> >>> >>>> http://grails.org/Download >>> >>>> >>> >>>> This release includes several new features and improvements since the >>> >>>> 2.0 release, including: >>> >>>> >>> >>>> * Improved Maven Support including multi-module builds >>> >>>> * An official caching solution via the new cache plugin (see >>> >>>> http://grails.org/plugin/cache) >>> >>>> * A new wrapper feature for building Grails applications without >>> >>>> requiring a Grails install >>> >>>> >>> >>>> For more information on these features please see the What's new >>> >>>> guide: http://grails.org/doc/2.1.0/guide/introduction.html#whatsNew21 >>> >>>> >>> >>>> We now are focusing on the 2.2 release which will include: >>> >>>> >>> >>>> * Groovy 2.0 >>> >>>> * Forked execution of run-app >>> >>>> * Namespace support >>> >>>> >>> >>>> The development time for 2.2 will be pretty short as we want to get >>> >>>> Groovy 2.0 in the hands of Grails developers as soon as possible so >>> >>>> expect a milestone in the next few weeks. >>> >>>> >>> >>>> Enjoy! >>> >>>> >>> >>>> -- >>> >>>> Graeme Rocher >>> >>>> Grails Project Lead >>> >>>> SpringSource - A Division of VMware >>> >>>> http://www.springsource.com >>> >>>> >>> >>>> --------------------------------------------------------------------- >>> >>>> To unsubscribe from this list, please visit: >>> >>>> >>> >>>> http://xircles.codehaus.org/manage_email >>> >>>> >>> >>>> >>> >>>> >>> >>>> --------------------------------------------------------------------- >>> >>>> To unsubscribe from this list, please visit: >>> >>>> >>> >>>> http://xircles.codehaus.org/manage_email >>> >>>> >>> >>>> >>> >>> >>> >> >>> > >>> > >>> > >>> > -- >>> > Graeme Rocher >>> > Grails Project Lead >>> > SpringSource - A Division of VMware >>> > http://www.springsource.com >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe from this list, please visit: >>> > >>> > http://xircles.codehaus.org/manage_email >>> > >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> > > > > -- > Graeme Rocher > Grails Project Lead > SpringSource - A Division of VMware > http://www.springsource.com -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: ANN: Grails 2.1 Released!
|
|
In reply to this post by Graeme Rocher-4
Just to make sure we're on the same page here: JBoss starts with a management application - that to say is a web application - thus my take on JBoss as something that does the apple-apple thing.
And don't get me wrong here - I love Groovy and Grails above anything else. I'd like it to be lighter and faster instead of being ever slower - that'd make the presentations (live coding mostly) I do a lot more fun :)
As for RoR - Well... Grails ideas are modeled after that platform. Both platforms do tend to borrow from each other (there's a "rails" command now in 3.x where there were just scripts in the pre-3.x version just to point out one similarity with Grails). Thus my take on comparing Grails with RoR...
As for interactive mode I did try it out, didn't like the idea very much from the start but out of necessity I am using it. Further more I don't like in 2.x the new console that looks like Gradle. It was sooo much more readable in 1.x :(
I'm just trying to say that from an agile and easy to get started framework that got me interested in web development Grails is becoming something big, fat and not necessarily good anymore. For me Grails was always about a small core and plugins that provided functionality that I needed, when I really needed it. It used to be a J2EE killer...
Matthias. 2012/7/6 Graeme Rocher <[hidden email]> You're talking Apples and Oranges here, you cannot compare starting up |
|
|
I'm with Matthias on this. I do love Grails, makes me productive as nothing else but I do have problems when I discuss its deployment with ops guys, specially when it comes to memory consumption. I don't mean to be rude or arrogant, I may have a wrong perception on Grails strategy (please correct if I'm wrong), but my perception is that Grails path has become all about delivering new stuff for developers, without caring about deployment, based on the assumption that memory is cheap and every app has a full tomcat dedicated to it. But this is not the reality for everyone. I work in a major oil company (which is obviously not fully agile), where we have to deal with multiple apps deployed on a shared weblogic instance, thus we can't have a single app consuming all the available memory. Some may say "that's what you get for working on a dinosaur company" but I don't think that's the way someone should be thinking when targetting massive adoption of a framework. Just like Matthias said, Grails is an excellent framework but if it gets fat and slow, things will just get out of the original track (if I have a correct perception of it). Anyway, maybe my case is an exception here, just wanted to bring my 2 cents to the thread. On Jul 6, 2012 8:55 AM, "Matthias Hryniszak" <[hidden email]> wrote:
Just to make sure we're on the same page here: JBoss starts with a management application - that to say is a web application - thus my take on JBoss as something that does the apple-apple thing. |
Re: ANN: Grails 2.1 Released!
|
I've been very happy with Grails. I find it to be very stable and performant in production. I haven't found it to be bloated or non-agile.
Development within IntelliJ 11.x is very enjoyable.
Yes, it uses more memory than a php or ruby app, but all Java based apps do. This tends to be a problem for those used to deploying to environments with 256m to 512m of memory. So far, Grails apps still run great on Amazon micro-instances. For my own selfish needs, I hope that continues to be the case.
I love the Java/Grails/Groovy ecosystem, the plugins, the libraries, the community, the fact that a Grails app deploys like any other war file, etc. Thanks and keep up the good work!
- Dean Del Ponte On Fri, Jul 6, 2012 at 7:45 AM, Felipe Carvalho <[hidden email]> wrote:
|
«
Return to Grails - user
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |