You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jim O'Callaghan <ji...@peritussolutions.com> on 2010/08/24 19:19:00 UTC
OT: Debugging Tapestry Apps using Eclipse
I'm facing an issue with my Eclipse IDE (3.4.1) and thought I would check if
anyone has faced the same issue / has a possible solution. I'm not sure
when this started (last few weeks) but I'm seeing a difference in
performance of over 10x between 'Run' and 'Debug' targets under Eclipse -
getting to the stage that dev is unworkable. I've used a variety of JDKs
from 1.5 up to 1.6u19, and have cycled the initial mem and max mem from 512m
up to 2048m, with a permgen between 256 - 512m. I'm using the eclipse jetty
plugin and running on a fast pc with plenty of RAM / disk space etc. When I
run this app as a 'Run' target under Eclipse, or from the command line the
response time is almost instant. Ring any bells with anyone? I'm trying
using one of the T 5.2.0 snapshot from a few months back
(5.2.0-20100603.111954-89) and also the current alpha. Startup / avg page
reponse is 50s / 30s with 'Debug' targets vs. 8s / almost instant with 'Run'
targets. Would be grateful for any advice.
Regards,
Jim.
RE: OT: Debugging Tapestry Apps using Eclipse
Posted by Jim O'Callaghan <jc...@yahoo.co.uk>.
Thanks for the response Josh. No breakpoints set. Any other thoughts
welcome.
Regards,
Jim.
-----Original Message-----
From: Josh Canfield [mailto:joshcanfield@gmail.com]
Sent: 24 August 2010 18:54
To: Tapestry users
Subject: Re: OT: Debugging Tapestry Apps using Eclipse
Off the top of my head it sounds like you might have a method breakpoint
set.. Have you tried clearing all of your breakpoints?
-- Josh
On Aug 24, 2010, at 10:19 AM, "Jim O'Callaghan" <ji...@peritussolutions.com>
wrote:
> I'm facing an issue with my Eclipse IDE (3.4.1) and thought I would check
if
> anyone has faced the same issue / has a possible solution. I'm not sure
> when this started (last few weeks) but I'm seeing a difference in
> performance of over 10x between 'Run' and 'Debug' targets under Eclipse -
> getting to the stage that dev is unworkable. I've used a variety of JDKs
> from 1.5 up to 1.6u19, and have cycled the initial mem and max mem from
512m
> up to 2048m, with a permgen between 256 - 512m. I'm using the eclipse
jetty
> plugin and running on a fast pc with plenty of RAM / disk space etc. When
I
> run this app as a 'Run' target under Eclipse, or from the command line the
> response time is almost instant. Ring any bells with anyone? I'm trying
> using one of the T 5.2.0 snapshot from a few months back
> (5.2.0-20100603.111954-89) and also the current alpha. Startup / avg page
> reponse is 50s / 30s with 'Debug' targets vs. 8s / almost instant with
'Run'
> targets. Would be grateful for any advice.
>
>
>
> Regards,
>
> Jim.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: OT: Debugging Tapestry Apps using Eclipse
Posted by Josh Canfield <jo...@gmail.com>.
Off the top of my head it sounds like you might have a method breakpoint set.. Have you tried clearing all of your breakpoints?
-- Josh
On Aug 24, 2010, at 10:19 AM, "Jim O'Callaghan" <ji...@peritussolutions.com> wrote:
> I'm facing an issue with my Eclipse IDE (3.4.1) and thought I would check if
> anyone has faced the same issue / has a possible solution. I'm not sure
> when this started (last few weeks) but I'm seeing a difference in
> performance of over 10x between 'Run' and 'Debug' targets under Eclipse -
> getting to the stage that dev is unworkable. I've used a variety of JDKs
> from 1.5 up to 1.6u19, and have cycled the initial mem and max mem from 512m
> up to 2048m, with a permgen between 256 - 512m. I'm using the eclipse jetty
> plugin and running on a fast pc with plenty of RAM / disk space etc. When I
> run this app as a 'Run' target under Eclipse, or from the command line the
> response time is almost instant. Ring any bells with anyone? I'm trying
> using one of the T 5.2.0 snapshot from a few months back
> (5.2.0-20100603.111954-89) and also the current alpha. Startup / avg page
> reponse is 50s / 30s with 'Debug' targets vs. 8s / almost instant with 'Run'
> targets. Would be grateful for any advice.
>
>
>
> Regards,
>
> Jim.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org