Group items tagged jsp - Google AppEngine

shared by Esfand S on 28 Sep 10 - No Cached

this tip can cut a few hundred milliseconds or more off of your cold start time. Using JSPs slows you down in two ways: If you have a file with a .jsp extension, anywhere in your website directory, appcfg will detect that you use JSP, and it will add 8 libraries that are used for processing JSPs into your lib directory before uploading to the app engine.  These libraries total two megabytes in size, and simply having them in your lib directory slows your cold starts down by a few hundred milliseconds. If you are interested in what libraries these are, you can see them in the temporary folder appcfg creates while uploading your app. The first JSP file accessed after a cold start, even an empty one, will take a few hundred additional milliseconds to be processed.  I'm not sure what causes this, maybe it has to do with initializing the JSP processor.
...

Cancel

shared by Esfand S on 28 Sep 10 - Cached

01<%@ page contentType="text/html" pageEncoding="UTF-8" %>02<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>03 04<!DOCTYPE html>05<html>06 <head>07  <title>Maintenance</title>08 </head>09<body>10 Hello from Spring ${user}11 AuthDomain = ${user.authDomain}12 Nickname = ${user.nickname}13 Email = ${user.email}14 UserId = ${user.userId}15</body>16</html>
...

Cancel

shared by Esfand S on 28 Sep 10 - Cached

shared by Esfand S on 28 Sep 10 - No Cached

Originally my application started out using Spring MVC and JDO. The first use of JDO took my application about 5 seconds to get everything set up.  Similarily, Spring MVC added around 6 seconds to the cold start  time
...

Cancel
 If you are not using either JDO or JPA, you can safely delete all related libraries (ones that have JDO, JPA, or Datanucleus in their name) and use the command line tool to upload your app. Deleting these libraries shaves about 400ms off of cold start time.
...

Cancel