GSP Compilation

[Sergei Rahouski]

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[bond_]

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" value="[phone]" target="_blank">[phone].

--

Thanks and regards,

Ravi Teja

[Sergei Rahouski]

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[bond_]

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

I don't think that this happens. Never occurred to me BTW

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" value="[phone]" target="_blank">[phone].

--

Thanks and regards,

Ravi Teja

[Sergei Rahouski]

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[bond_]

I know this but looks like you're on a pretty large GSP page. On the projects that I've worked on it would take 1-3 seconds the first time.

On Wed, Aug 8, 2012 at 8:40 PM, Sergei Rahouski <[hidden email]> wrote:

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" value="[phone]" target="_blank">[phone].

--

Thanks and regards,

Ravi Teja

[Sergei Rahouski]

It is a big project but even for you it would help if you didn’t need to wait 3 seconds. It bites you the most if you do a lot of functional testing.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:20 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I know this but looks like you're on a pretty large GSP page. On the projects that I've worked on it would take 1-3 seconds the first time.

On Wed, Aug 8, 2012 at 8:40 PM, Sergei Rahouski <[hidden email]> wrote:

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[bond_]

Geb is there to save the day  for us.

On Wed, Aug 8, 2012 at 8:58 PM, Sergei Rahouski <[hidden email]> wrote:

It is a big project but even for you it would help if you didn’t need to wait 3 seconds. It bites you the most if you do a lot of functional testing.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:20 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I know this but looks like you're on a pretty large GSP page. On the projects that I've worked on it would take 1-3 seconds the first time.

On Wed, Aug 8, 2012 at 8:40 PM, Sergei Rahouski <[hidden email]> wrote:

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" value="[phone]" target="_blank">[phone].

--

Thanks and regards,

Ravi Teja

[Sergei Rahouski]

We use geb too , it is very slow. It needs to compile each GSP page you use in the test, we get timeouts all the time because of the compilation issue. So if you have a test that goes through 3 pages, it would spend 9 seconds in your case compiling the pages and may b1 second to run the actual test.

 

How is that working for you?

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:33 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

Geb is there to save the day  for us.

On Wed, Aug 8, 2012 at 8:58 PM, Sergei Rahouski <[hidden email]> wrote:

It is a big project but even for you it would help if you didn’t need to wait 3 seconds. It bites you the most if you do a lot of functional testing.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:20 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I know this but looks like you're on a pretty large GSP page. On the projects that I've worked on it would take 1-3 seconds the first time.

On Wed, Aug 8, 2012 at 8:40 PM, Sergei Rahouski <[hidden email]> wrote:

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[bond_]

Time wasn't an issue in our case Jenkins runs the functional builds for us. We have like 18 testclasses and takes around 10-15 min to complete the build.

Check if you can make your gsp lighter. Probably externalize your JavaScript and CSS. Use templating feature of gsp.

On Aug 8, 2012 9:10 PM, "Sergei Rahouski" <[hidden email]> wrote:

We use geb too , it is very slow. It needs to compile each GSP page you use in the test, we get timeouts all the time because of the compilation issue. So if you have a test that goes through 3 pages, it would spend 9 seconds in your case compiling the pages and may b1 second to run the actual test.

 

How is that working for you?

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:33 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

Geb is there to save the day  for us.

On Wed, Aug 8, 2012 at 8:58 PM, Sergei Rahouski <[hidden email]> wrote:

It is a big project but even for you it would help if you didn’t need to wait 3 seconds. It bites you the most if you do a lot of functional testing.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:20 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I know this but looks like you're on a pretty large GSP page. On the projects that I've worked on it would take 1-3 seconds the first time.

On Wed, Aug 8, 2012 at 8:40 PM, Sergei Rahouski <[hidden email]> wrote:

It is simple to test:

 

1)      Start your server

2)      Hit a GSP – your load time will be 1-2 seconds on a small GSP (we’ve seen 25 seconds on larger GSPs)

3)      Hit the GSP again you get microsecond response.

 

What’s the difference between the first use and subsequent? … compilation time.

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 10:06 AM

To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

 

On Wed, Aug 8, 2012 at 8:28 PM, Sergei Rahouski <[hidden email]> wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled,

 

I don't think that this happens. Never occurred to me BTW

 

 

or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

This question needs to be answered by the maintainers IMHO.

 

 

From: Raviteja Lokineni [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" value="[phone]" target="_blank">[phone].

[Lari Hotari]

OK, I understand your point , I'm listening. :)

In development mode, GSPs get compiled on-demand when they are used the first time. The compiled GSPs are only cached in memory in this case.
I have worked with large applications that build a single URL request from about 20-30 separate GSP templates and there hasn't been any serious problems with performance in development mode.

How many GSP pages/templates does your application have? How many different templates does a single request use and how long does it take to full-fill the request?
What version of Grails are you using? If you are using Grails 2.x , have you tried with "reloading agent" turned off (grails -noreloading) ? Does is it make any difference?

Are you willing to provide a test app that reproduces the possible performance problem ? (I just want to be sure that it's the GSP compilation that is the bottleneck.)

Lari


08.08.2012 17:58, Sergei Rahouski wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

From: Raviteja Lokineni [[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a moz-do-not-send="true" href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[Sergei Rahouski]

The application is large. We have around 600 GSP files and we are about 30% done.  So a rough estimate would be 2000 GSP files when the project is done.

 

Some of GSP pages are big we render 6-10 panels on a page each of them is a separate GSP template. We are on Grails 1.3.7, panning to upgrade to 2.1 probably in September.

 

Just to clarify the problem there are 2 scenarios we are struggling with:

1)      We have to restart pretty often for reasons. After restart the developer usually needs to go to the same page where he/she was. This path takes about 3-4 pages to get back – login / index / search what not. Each of them take time , you end up on a page and see it crashed again. Very inefficient in many cases.

2)      Testing integration with different parts of the application. Example: developers finished his task and verifies if outgoing links to other parts of the app work. Causes recompilation of the pages he/she didn’t touch on every restart again. Takes more time than it needs do.

3)      Now the killer – Geb test development. This is a process that hurts the most. We would like to write test cases around 6-10 steps long. They login go through index page and such to land on a target page then we do cross page tests. Each step takes forever to develop as mistakes in Geb tests are often (wrong selector or something). You have to restart the whole test. You end up spending 6-8 ours on a test that runs for 30 seconds. Geb tests often go between pages , and every time it hits a new page it requires compilation, by the time we execute the test the code base is rather stable, there are no changes in views or in grails-app folder during this process, yet we are spending hours compiling GSPs.

 

Example … I can come up with an example but any page will do, you can just put some static text may be 5-10k lines of text or javascript in a GSP page. The problem is that even if it takes 3 seconds for each compile , it is slow. If it is 10-20 it is very bad.

 

Thanks for replying.

 

From: Lari Hotari [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 12:19 PM
To: [hidden email]
Cc: Sergei Rahouski
Subject: Re: [grails-user] GSP Compilation

 

OK, I understand your point , I'm listening. :)

In development mode, GSPs get compiled on-demand when they are used the first time. The compiled GSPs are only cached in memory in this case.
I have worked with large applications that build a single URL request from about 20-30 separate GSP templates and there hasn't been any serious problems with performance in development mode.

How many GSP pages/templates does your application have? How many different templates does a single request use and how long does it take to full-fill the request?
What version of Grails are you using? If you are using Grails 2.x , have you tried with "reloading agent" turned off (grails -noreloading) ? Does is it make any difference?

Are you willing to provide a test app that reproduces the possible performance problem ? (I just want to be sure that it's the GSP compilation that is the bottleneck.)

Lari


08.08.2012 17:58, Sergei Rahouski wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

From: Raviteja Lokineni [[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[Lari Hotari]

Hi,

I reopened http://jira.grails.org/browse/GRAILS-6183 .

Lari

off-topic:
btw. One feature that I've been longing for is the possibility to have 2 levels of "clean". I'd like to have plugins compiled and only "cleaned" with a separate command. This would make normal plugins behave more or less like binary plugins without having to really make them binary plugins. Plugin compilation time has taken most of the time for me.


08.08.2012 20:41, Sergei Rahouski wrote:

The application is large. We have around 600 GSP files and we are about 30% done.  So a rough estimate would be 2000 GSP files when the project is done.

 

Some of GSP pages are big we render 6-10 panels on a page each of them is a separate GSP template. We are on Grails 1.3.7, panning to upgrade to 2.1 probably in September.

 

Just to clarify the problem there are 2 scenarios we are struggling with:

1)      We have to restart pretty often for reasons. After restart the developer usually needs to go to the same page where he/she was. This path takes about 3-4 pages to get back – login / index / search what not. Each of them take time , you end up on a page and see it crashed again. Very inefficient in many cases.

2)      Testing integration with different parts of the application. Example: developers finished his task and verifies if outgoing links to other parts of the app work. Causes recompilation of the pages he/she didn’t touch on every restart again. Takes more time than it needs do.

3)      Now the killer – Geb test development. This is a process that hurts the most. We would like to write test cases around 6-10 steps long. They login go through index page and such to land on a target page then we do cross page tests. Each step takes forever to develop as mistakes in Geb tests are often (wrong selector or something). You have to restart the whole test. You end up spending 6-8 ours on a test that runs for 30 seconds. Geb tests often go between pages , and every time it hits a new page it requires compilation, by the time we execute the test the code base is rather stable, there are no changes in views or in grails-app folder during this process, yet we are spending hours compiling GSPs.

 

Example … I can come up with an example but any page will do, you can just put some static text may be 5-10k lines of text or javascript in a GSP page. The problem is that even if it takes 3 seconds for each compile , it is slow. If it is 10-20 it is very bad.

 

Thanks for replying.

 

From: Lari Hotari [[hidden email]]
Sent: Wednesday, August 08, 2012 12:19 PM
To: [hidden email]
Cc: Sergei Rahouski
Subject: Re: [grails-user] GSP Compilation

 

OK, I understand your point , I'm listening. :)

In development mode, GSPs get compiled on-demand when they are used the first time. The compiled GSPs are only cached in memory in this case.
I have worked with large applications that build a single URL request from about 20-30 separate GSP templates and there hasn't been any serious problems with performance in development mode.

How many GSP pages/templates does your application have? How many different templates does a single request use and how long does it take to full-fill the request?
What version of Grails are you using? If you are using Grails 2.x , have you tried with "reloading agent" turned off (grails -noreloading) ? Does is it make any difference?

Are you willing to provide a test app that reproduces the possible performance problem ? (I just want to be sure that it's the GSP compilation that is the bottleneck.)

Lari


08.08.2012 17:58, Sergei Rahouski wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

From: Raviteja Lokineni [[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira   it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling <a moz-do-not-send="true" href="tel:%2B1%20%28612%29%20851-3200" target="_blank">[phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[zenith_amit]

For the Geb tests, we have created a different grails project. The main application and geb are configured to run on different ports and can run simultaneously. Also you can restart geb as frequently as you want.

---

From: Sergei Rahouski <[hidden email]>
To: [hidden email]
Sent: Wednesday, 8 August 2012 1:41 PM
Subject: RE: [grails-user] GSP Compilation

The application is large. We have around 600 GSP files and we are about 30% done.  So a rough estimate would be 2000 GSP files when the project is done.

 

Some of GSP pages are big we render 6-10 panels on a page each of them is a separate GSP template. We are on Grails 1.3.7, panning to upgrade to 2.1 probably in September.

 

Just to clarify the problem there are 2 scenarios we are struggling with:

1)      We have to restart pretty often for reasons. After restart the developer usually needs to go to the same page where he/she was. This path takes about 3-4 pages to get back – login / index / search what not. Each of them take time , you end up on a page and see it crashed again. Very inefficient in many cases.

2)      Testing integration with different parts of the application. Example: developers finished his task and verifies if outgoing links to other parts of the app work. Causes recompilation of the pages he/she didn’t touch on every restart again. Takes more time than it needs do.

3)      Now the killer – Geb test development. This is a process that hurts the most. We would like to write test cases around 6-10 steps long. They login go through index page and such to land on a target page then we do cross page tests. Each step takes forever to develop as mistakes in Geb tests are often (wrong selector or something). You have to restart the whole test. You end up spending 6-8 ours on a test that runs for 30 seconds. Geb tests often go between pages , and every time it hits a new page it requires compilation, by the time we execute the test the code base is rather stable, there are no changes in views or in grails-app folder during this process, yet we are spending hours compiling GSPs.

 

Example … I can come up with an example but any page will do, you can just put some static text may be 5-10k lines of text or javascript in a GSP page. The problem is that even if it takes 3 seconds for each compile , it is slow. If it is 10-20 it is very bad.

 

Thanks for replying.

 

From: Lari Hotari [mailto:[hidden email]]
Sent: Wednesday, August 08, 2012 12:19 PM
To: [hidden email]
Cc: Sergei Rahouski
Subject: Re: [grails-user] GSP Compilation

 

OK, I understand your point , I'm listening. :)

In development mode, GSPs get compiled on-demand when they are used the first time. The compiled GSPs are only cached in memory in this case.
I have worked with large applications that build a single URL request from about 20-30 separate GSP templates and there hasn't been any serious problems with performance in development mode.

How many GSP pages/templates does your application have? How many different templates does a single request use and how long does it take to full-fill the request?
What version of Grails are you using? If you are using Grails 2.x , have you tried with "reloading agent" turned off (grails -noreloading) ? Does is it make any difference?

Are you willing to provide a test app that reproduces the possible performance problem ? (I just want to be sure that it's the GSP compilation that is the bottleneck.)

Lari


08.08.2012 17:58, Sergei Rahouski wrote:

We use development mode for day to day development. We are restarting because we need to restart not to cause a problem , there are hundreds of reasons for you to restart the application.

 

You are right GSPs get recompiled automatically. That is exactly the problem. If I modify one GSP I don’t want other GSP files to be recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.

 

… or even better if I haven’t modified ANYTHING in the project I don’t want to recompile GSP.

 

Makes sense?

 

From: Raviteja Lokineni [[hidden email]]
Sent: Wednesday, August 08, 2012 9:50 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

 

I have a few questions:

1. Why are you restarting?
2. Is it in dev environment or production?

If it is for development mode GSP(s) recompile automatically no need to restart.

On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]> wrote:

We are developing a large application (more than 50 developers). The fact that we need to recompile GSP pages on every restart really hurts us – we are wasting development time and not able to efficiently implement functional tests.

 

When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it made me really sad and worried. This is a very good feature request. I cannot imagine any descent Grails application that wouldn’t benefit from the suggested fix.

 

If there are any Grails core developers reading this post, I suggest you actually try using your own framework in a large application and suffer from those things every day. This will allow you to make better calls closing issues.

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

 

--

Thanks and regards,

Ravi Teja

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

 

This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[Antony Jones]

I agree that initial compliation of a page can make a Geb test fail, I
too have seen this, and my gsps certainly aren't that large. A modal
dialog which loads a template can take more than 5 seconds on first
attempt.

However I don't know why modifying a Geb tests gives you cause to
restart the tomcat container. During grails development, using some
types of object in a Service or Controller can break the container
reloading (with a UserService cannot be cast to UserService) type
error - but NEVER in a Geb test - you can modify those forever.

Cheers,
Antony

On 9 August 2012 04:18, Amit Srivastava <[hidden email]> wrote:

> For the Geb tests, we have created a different grails project. The main
> application and geb are configured to run on different ports and can run
> simultaneously. Also you can restart geb as frequently as you want.
>
> ________________________________
> From: Sergei Rahouski <[hidden email]>
> To: [hidden email]
> Sent: Wednesday, 8 August 2012 1:41 PM
> Subject: RE: [grails-user] GSP Compilation
>
> The application is large. We have around 600 GSP files and we are about 30%
> done.  So a rough estimate would be 2000 GSP files when the project is done.
>
> Some of GSP pages are big we render 6-10 panels on a page each of them is a
> separate GSP template. We are on Grails 1.3.7, panning to upgrade to 2.1
> probably in September.
>
> Just to clarify the problem there are 2 scenarios we are struggling with:
> 1)      We have to restart pretty often for reasons. After restart the
> developer usually needs to go to the same page where he/she was. This path
> takes about 3-4 pages to get back – login / index / search what not. Each of
> them take time , you end up on a page and see it crashed again. Very
> inefficient in many cases.
> 2)      Testing integration with different parts of the application.
> Example: developers finished his task and verifies if outgoing links to
> other parts of the app work. Causes recompilation of the pages he/she didn’t
> touch on every restart again. Takes more time than it needs do.
> 3)      Now the killer – Geb test development. This is a process that hurts
> the most. We would like to write test cases around 6-10 steps long. They
> login go through index page and such to land on a target page then we do
> cross page tests. Each step takes forever to develop as mistakes in Geb
> tests are often (wrong selector or something). You have to restart the whole
> test. You end up spending 6-8 ours on a test that runs for 30 seconds. Geb
> tests often go between pages , and every time it hits a new page it requires
> compilation, by the time we execute the test the code base is rather stable,
> there are no changes in views or in grails-app folder during this process,
> yet we are spending hours compiling GSPs.
>
> Example … I can come up with an example but any page will do, you can just
> put some static text may be 5-10k lines of text or javascript in a GSP page.
> The problem is that even if it takes 3 seconds for each compile , it is
> slow. If it is 10-20 it is very bad.
>
> Thanks for replying.
>
> From: Lari Hotari [mailto:[hidden email]]
> Sent: Wednesday, August 08, 2012 12:19 PM
> To: [hidden email]
> Cc: Sergei Rahouski
> Subject: Re: [grails-user] GSP Compilation
>
> OK, I understand your point , I'm listening. :)
>
> In development mode, GSPs get compiled on-demand when they are used the
> first time. The compiled GSPs are only cached in memory in this case.
> I have worked with large applications that build a single URL request from
> about 20-30 separate GSP templates and there hasn't been any serious
> problems with performance in development mode.
>
> How many GSP pages/templates does your application have? How many different
> templates does a single request use and how long does it take to full-fill
> the request?
> What version of Grails are you using? If you are using Grails 2.x , have you
> tried with "reloading agent" turned off (grails -noreloading) ? Does is it
> make any difference?
>
> Are you willing to provide a test app that reproduces the possible
> performance problem ? (I just want to be sure that it's the GSP compilation
> that is the bottleneck.)
>
> Lari
>
>
> 08.08.2012 17:58, Sergei Rahouski wrote:
>
> We use development mode for day to day development. We are restarting
> because we need to restart not to cause a problem , there are hundreds of
> reasons for you to restart the application.
>
> You are right GSPs get recompiled automatically. That is exactly the
> problem. If I modify one GSP I don’t want other GSP files to be recompiled,
> or if I haven’t modify any GSPs I don’t want them to be recompiled.
>
> … or even better if I haven’t modified ANYTHING in the project I don’t want
> to recompile GSP.
>
> Makes sense?
>
> From: Raviteja Lokineni [mailto:[hidden email]]
> Sent: Wednesday, August 08, 2012 9:50 AM
> To: [hidden email]
> Subject: Re: [grails-user] GSP Compilation
>
> I have a few questions:
>
> Why are you restarting?
> Is it in dev environment or production?
>
> If it is for development mode GSP(s) recompile automatically no need to
> restart.
> On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]>
> wrote:
> We are developing a large application (more than 50 developers). The fact
> that we need to recompile GSP pages on every restart really hurts us – we
> are wasting development time and not able to efficiently implement
> functional tests.
>
> When I came across this Jira  http://jira.grails.org/browse/GRAILS-6183 it
> made me really sad and worried. This is a very good feature request. I
> cannot imagine any descent Grails application that wouldn’t benefit from the
> suggested fix.
>
> If there are any Grails core developers reading this post, I suggest you
> actually try using your own framework in a large application and suffer from
> those things every day. This will allow you to make better calls closing
> issues.
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information. If
> you receive this message in error or are not the intended recipient, you may
> not disseminate this message and you are requested to erase all copies of
> this message and its attachments and contact the sender by email or by
> calling [phone].
>
>
>
> --
> Thanks and regards,
> Ravi Teja
>
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information. If
> you receive this message in error or are not the intended recipient, you may
> not disseminate this message and you are requested to erase all copies of
> this message and its attachments and contact the sender by email or by
> calling [phone].
>
>
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information. If
> you receive this message in error or are not the intended recipient, you may
> not disseminate this message and you are requested to erase all copies of
> this message and its attachments and contact the sender by email or by
> calling [phone].
>
>

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Sergei Rahouski]

When we run test-app functional:spock it starts the application on port 8090 for us and at this time it recompiles the GSPs.

Is this how your run your Geb test in development too? I am hoping to learn a better method of running Geb tests in development.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Antony Jones
Sent: Thursday, August 09, 2012 1:08 AM
To: [hidden email]
Subject: Re: [grails-user] GSP Compilation

I agree that initial compliation of a page can make a Geb test fail, I too have seen this, and my gsps certainly aren't that large. A modal dialog which loads a template can take more than 5 seconds on first attempt.

However I don't know why modifying a Geb tests gives you cause to restart the tomcat container. During grails development, using some types of object in a Service or Controller can break the container reloading (with a UserService cannot be cast to UserService) type error - but NEVER in a Geb test - you can modify those forever.

Cheers,
Antony

On 9 August 2012 04:18, Amit Srivastava <[hidden email]> wrote:

> For the Geb tests, we have created a different grails project. The
> main application and geb are configured to run on different ports and
> can run simultaneously. Also you can restart geb as frequently as you want.
>
> ________________________________
> From: Sergei Rahouski <[hidden email]>
> To: [hidden email]
> Sent: Wednesday, 8 August 2012 1:41 PM
> Subject: RE: [grails-user] GSP Compilation
>
> The application is large. We have around 600 GSP files and we are
> about 30% done.  So a rough estimate would be 2000 GSP files when the project is done.
>
> Some of GSP pages are big we render 6-10 panels on a page each of them
> is a separate GSP template. We are on Grails 1.3.7, panning to upgrade
> to 2.1 probably in September.
>
> Just to clarify the problem there are 2 scenarios we are struggling with:
> 1)      We have to restart pretty often for reasons. After restart the
> developer usually needs to go to the same page where he/she was. This
> path takes about 3-4 pages to get back – login / index / search what
> not. Each of them take time , you end up on a page and see it crashed
> again. Very inefficient in many cases.
> 2)      Testing integration with different parts of the application.
> Example: developers finished his task and verifies if outgoing links
> to other parts of the app work. Causes recompilation of the pages
> he/she didn’t touch on every restart again. Takes more time than it needs do.
> 3)      Now the killer – Geb test development. This is a process that hurts
> the most. We would like to write test cases around 6-10 steps long.
> They login go through index page and such to land on a target page
> then we do cross page tests. Each step takes forever to develop as
> mistakes in Geb tests are often (wrong selector or something). You
> have to restart the whole test. You end up spending 6-8 ours on a test
> that runs for 30 seconds. Geb tests often go between pages , and every
> time it hits a new page it requires compilation, by the time we
> execute the test the code base is rather stable, there are no changes
> in views or in grails-app folder during this process, yet we are spending hours compiling GSPs.
>
> Example … I can come up with an example but any page will do, you can
> just put some static text may be 5-10k lines of text or javascript in a GSP page.
> The problem is that even if it takes 3 seconds for each compile , it
> is slow. If it is 10-20 it is very bad.
>
> Thanks for replying.
>
> From: Lari Hotari [mailto:[hidden email]]
> Sent: Wednesday, August 08, 2012 12:19 PM
> To: [hidden email]
> Cc: Sergei Rahouski
> Subject: Re: [grails-user] GSP Compilation
>
> OK, I understand your point , I'm listening. :)
>
> In development mode, GSPs get compiled on-demand when they are used
> the first time. The compiled GSPs are only cached in memory in this case.
> I have worked with large applications that build a single URL request
> from about 20-30 separate GSP templates and there hasn't been any
> serious problems with performance in development mode.
>
> How many GSP pages/templates does your application have? How many
> different templates does a single request use and how long does it
> take to full-fill the request?
> What version of Grails are you using? If you are using Grails 2.x ,
> have you tried with "reloading agent" turned off (grails -noreloading)
> ? Does is it make any difference?
>
> Are you willing to provide a test app that reproduces the possible
> performance problem ? (I just want to be sure that it's the GSP
> compilation that is the bottleneck.)
>
> Lari
>
>
> 08.08.2012 17:58, Sergei Rahouski wrote:
>
> We use development mode for day to day development. We are restarting
> because we need to restart not to cause a problem , there are hundreds
> of reasons for you to restart the application.
>
> You are right GSPs get recompiled automatically. That is exactly the
> problem. If I modify one GSP I don’t want other GSP files to be
> recompiled, or if I haven’t modify any GSPs I don’t want them to be recompiled.
>
> … or even better if I haven’t modified ANYTHING in the project I don’t
> want to recompile GSP.
>
> Makes sense?
>
> From: Raviteja Lokineni [mailto:[hidden email]]
> Sent: Wednesday, August 08, 2012 9:50 AM
> To: [hidden email]
> Subject: Re: [grails-user] GSP Compilation
>
> I have a few questions:
>
> Why are you restarting?
> Is it in dev environment or production?
>
> If it is for development mode GSP(s) recompile automatically no need
> to restart.
> On Wed, Aug 8, 2012 at 7:39 PM, Sergei Rahouski <[hidden email]>
> wrote:
> We are developing a large application (more than 50 developers). The
> fact that we need to recompile GSP pages on every restart really hurts
> us – we are wasting development time and not able to efficiently
> implement functional tests.
>
> When I came across this Jira  
> http://jira.grails.org/browse/GRAILS-6183 it made me really sad and
> worried. This is a very good feature request. I cannot imagine any
> descent Grails application that wouldn’t benefit from the suggested fix.
>
> If there are any Grails core developers reading this post, I suggest
> you actually try using your own framework in a large application and
> suffer from those things every day. This will allow you to make better
> calls closing issues.
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information.
> If you receive this message in error or are not the intended
> recipient, you may not disseminate this message and you are requested
> to erase all copies of this message and its attachments and contact
> the sender by email or by calling [phone].
>
>
>
> --
> Thanks and regards,
> Ravi Teja
>
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information.
> If you receive this message in error or are not the intended
> recipient, you may not disseminate this message and you are requested
> to erase all copies of this message and its attachments and contact
> the sender by email or by calling [phone].
>
>
> This message and any attachments originate from International Decision
> Systems (IDS) and contains privileged and/or confidential information.
> If you receive this message in error or are not the intended
> recipient, you may not disseminate this message and you are requested
> to erase all copies of this message and its attachments and contact
> the sender by email or by calling [phone].
>
>

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


This message and any attachments originate from International Decision Systems (IDS) and contains privileged and/or confidential information. If you receive this message in error or are not the intended recipient, you may not disseminate this message and you are requested to erase all copies of this message and its attachments and contact the sender by email or by calling [phone].

[alxndrsn]

On 9 August 2012 09:08, Antony Jones <[hidden email]> wrote:
> I agree that initial compliation of a page can make a Geb test fail, I
> too have seen this, and my gsps certainly aren't that large. A modal
> dialog which loads a template can take more than 5 seconds on first
> attempt.
Ditto here.  Are we all doing something wrong?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[bond_]

WRT modal dialog. I would construct the modal dialog on page load and mark it as 'display:none' and when the modal dialog is displayed I would only fetch data(not via gsp).

On Fri, Aug 10, 2012 at 6:28 PM, Alex Anderson <[hidden email]> wrote:

On 9 August 2012 09:08, Antony Jones <[hidden email]> wrote:
> I agree that initial compliation of a page can make a Geb test fail, I
> too have seen this, and my gsps certainly aren't that large. A modal
> dialog which loads a template can take more than 5 seconds on first
> attempt.

Ditto here.  Are we all doing something wrong?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

--

Thanks and regards,

Ravi Teja

[alxndrsn]

On 10 August 2012 17:18, Raviteja Lokineni <[hidden email]> wrote:
> WRT modal dialog. I would construct the modal dialog on page load and mark
> it as 'display:none' and when the modal dialog is displayed I would only
> fetch data(not via gsp).

Is there a reason you would recommend this approach?  It's probably
impractical for us, as there are a lot of different dialogs we might
display.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[bond_]

Hmm well depends on the requirement though. I like the browser to do the heavy lifting of the UI stuff and keep the processing of data to the server side.

On Aug 10, 2012 9:46 PM, "Alex Anderson" <[hidden email]> wrote:

On 10 August 2012 17:18, Raviteja Lokineni <[hidden email]> wrote:
> WRT modal dialog. I would construct the modal dialog on page load and mark
> it as 'display:none' and when the modal dialog is displayed I would only
> fetch data(not via gsp).

Is there a reason you would recommend this approach?  It's probably
impractical for us, as there are a lot of different dialogs we might
display.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email