On a rough and read benchmark I can confirm that on an entirely
domain-manipulation based operation (processing '000s of records from a
legacy database into a domain structure) with just one view, cpu time
spent in the application went from about 150s to about 20s. BTW if I'd
realised quite how simple the deployment was I wouldn't have bothered
asking :-). My first attempt to set up a web application server by
myself and deploy a grails app took less than 15 minutes including time
taken to download jboss - so thanks very much for the effort put into
the war building side of things.
-----Original Message-----
From:
graeme.rocher@... [mailto:
graeme.rocher@...] On Behalf
Of Graeme Rocher
Sent: 07 December 2007 11:55
To:
user@...
Subject: Re: [grails-user] jetty vs "proper" application servers -
performance
Yes there will be a big different. Not because of jetty itself, but
because in developer Grails reloads changes at runtime and doesn't
cache views
It will be orders of maginitude faster
Cheers
On Dec 7, 2007 11:38 AM, Tim Pigden <
tim.pigden@...> wrote:
>
>
>
>
> Would I expect significant changes in performance between running
under
> Jetty in development mode and deployed? I haven't yet had a chance to
> experiment. I'm assuming there won't be a big difference but I would
be
> interested in what you guys have found.
>
>
>
> Thanks
>
>
>
> Tim Pigden
>
> Optrak Distribution Software Limited
>
> Orland House
>
> Mead Lane
>
> Hertford
>
> SG13 7AT
>
> Tel: 01992 517100
>
> www.optrak.co.uk
>
>
--
Graeme Rocher
Grails Project Lead
G2One, Inc. Chief Technology Officer
http://www.g2one.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
