I now precompile my JSPs before deploying to production and they execute pretty fast there. But I still have the same problem with my local dev environment: takes about 3mns to compile any simple page, which do not even access the datastore.
I've been meaning to profile all this but have not had time yet. I upgraded to SDK 1.3.0 and still seeing the problem. On Jan 10, 4:09 am, Simon Vogensen <[email protected]> wrote: > Hi > > When I start my project with appengine alone (without gwt devmode) it > compiles fast - so this may be a problem with AppEngineLauncher? > > Here's my target starting appengine > > <target name="server" description="Run the AppEngine development > server"> > <echo message="PLEASE BROWSE TO:http://localhost:8080/${gwt.startupUrl}"/> > <java > classname="com.google.appengine.tools.development.DevAppServerMain" > classpath="${appengine.sdk}/lib/appengine-tools-api.jar" fork="yes"> > <arg value="war" /> > <jvmarg value="-javaagent:${appengine.sdk}/lib/agent/appengine- > agent.jar"/> > </java> > </target> > > Cheers > Simon > > On Dec 30 2009, 8:29 pm, Simon Vogensen <[email protected]> wrote: > > > > > Hi again > > > The funny thing is that on my machine (a macbook pro 2.66 ghz dual > > core) all jsp files takes about 1:45 minutes to compile.. even the > > ones with no logic.. > > > Cheers > > Simon > > > On Dec 30, 2:50 pm, Simon Vogensen <[email protected]> wrote: > > > > Hi > > > > Im having the same problems.. every time I change a .jsp file it takes > > > up to 3 min to recompile it.. > > > My project is very small, there's almost no data in the datastore. The > > > jsp file is also very small. > > > I should say that im running appengine through devmode on a mac with > > > snow leopard. > > > I have tried profiling with Visualvm and get the following hotspots > > > (this shows the load of one jsp recompile).. > > > > org.apache.tools.ant.taskdefs.StreamPumper.run() 40.26772 > > > 208150 ms > > > (40.3%) 2 > > > org.mortbay.jetty.Server.handle(org.mortbay.jetty.HttpConnection) > > > 20.24753 104662 ms (20.2%) 13 > > > java.lang.UNIXProcess$2$1.run() 20.171682 104270 ms (20.2%) 1 > > > java.util.concurrent.ThreadPoolExecutor$Worker.run() 10.060698 > > > 52005 > > > ms (10.1%) 1 > > > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run() 9.137142 > > > 47231 ms (9.1%) 2 > > > com.google.appengine.api.datastore.dev.LocalDatastoreService.runQuery > > > (com.google.appengine.tools.development.LocalRpcService.Status, > > > com.google.apphosting.api.DatastorePb.Query) 0.0101551 58.5 ms (0%) 11 > > > > Most of the time when recompiling it seems its waiting for IO or > > > something - the cpu is almost idle. > > > > My ant target looks like this.. > > > > <target name="devmode" depends="javac" description="Run development > > > mode"> > > > <java failonerror="true" fork="true" > > > classname="com.google.gwt.dev.DevMode"> > > > <classpath> > > > <pathelement location="src"/> > > > <path refid="project.class.path"/> > > > <path refid="tools.class.path"/> > > > </classpath> > > > <jvmarg value="-Xmx512M"/> > > > <jvmarg value="-javaagent:${appengine.sdk}/lib/agent/appengine- > > > agent.jar"/> > > > <jvmarg value="-Xdebug"/> > > > <jvmarg value="- > > > Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"/> > > > <arg value="-startupUrl"/> > > > <arg value="${gwt.startupUrl}"/> > > > <!-- Additional arguments like -style PRETTY or -logLevel DEBUG > > > --> > > > <arg value="-server"/> > > > <arg > > > value="com.google.appengine.tools.development.gwt.AppEngineLauncher"/> > > > <arg value="${gwt.module}"/> > > > </java> > > > </target> > > > > Cheers > > > Simon > > > > On Nov 17, 6:04 pm, Toby Reyelts <[email protected]> wrote: > > > > > On Sat, Nov 14, 2009 at 1:01 PM, Steph <[email protected]> wrote: > > > > > This happens: > > > > > - running dev_appserver > > > > > - with JSP files of just any size. > > > > > - seems to be blocking on initializing the datastore > > > > > Can you elaborate on this part a bit more? What are you seeing that > > > > makes > > > > you think it's "initializing the datastore"? Are you restarting the > > > > entire > > > > dev_appserver after modifying the jsp? How large is your datastore > > > > (e.g. how > > > > many entities, how many properties per entity, average size of each > > > > property). > > > > > If you can file an issue with a very simple webapp that reproduces the > > > > problem, that would be the best way for us to track the problem down. > > > > Alternatively, you could hook a profiler up to the dev_appserver > > > > yourself > > > > (for example, visualvm, hprof, or jprofiler). With three minutes of > > > > execution time, there should be a pretty obvious hotspot. > > > > > > I tried to set --jvm_flag=-Xmx1G in my dev_appserver.cmd file but it > > > > > does not seem to help much (i don't use eclipse) > > > > > Another other advice? > > > > > > On Nov 13, 12:00 pm, Toby Reyelts <[email protected]> wrote: > > > > > > Wow, that sounds bad. You're saying that this happens while running > > > > > > the > > > > > > dev_appserver (not appcfg), and you're only modifying one JSP file? > > > > > > Is > > > > > that > > > > > > JSP file huge? Try raising the heap size of your JVM. For example, > > > > > > if > > > > > you're > > > > > > using Eclipse, set -Xmx1G in the JVM arguments for your launch > > > > > > config. If > > > > > > you're running the dev_appserver from the command line, use > > > > > > --jvm_flag=-Xmx1G.On Fri, Nov 13, 2009 at 12:51 PM, Steph < > > > > > [email protected]> wrote: > > > > > > > When modifying a JSP in the war directory, it can take up to 3 > > > > > > > minutes > > > > > > > for the JSP to recompile and the page to render (I am on a brand > > > > > > > new > > > > > > > dual-core CPU 2.66 Ghz). > > > > > > > > Is there a way that the JSP compile time can be speed up? This > > > > > > > slowness makes development almost unbearable. Thanks for your > > > > > > > help. > > > > > > > > -- > > > > > > > > You received this message because you are subscribed to the Google > > > > > Groups > > > > > > > "Google App Engine for Java" group. > > > > > > > To post to this group, send email to > > > > > > > [email protected]. > > > > > > > To unsubscribe from this group, send email to > > > > > > > [email protected]<google-appengine-java%2B > > > > > > > [email protected]><google-appengine-java%2B > > > > > [email protected]> > > > > > > > . > > > > > > > For more options, visit this group at > > > > > > >http://groups.google.com/group/google-appengine-java?hl=. > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > Groups > > > > > "Google App Engine for Java" group. > > > > > To post to this group, send email to > > > > > [email protected]. > > > > > To unsubscribe from this group, send email to > > > > > [email protected]<google-appengine-java%2B > > > > > [email protected]> > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/google-appengine-java?hl=.
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
