[google-appengine] Re: Why are cloud endpoints so slow ?
Don't get me wrong - I absolutely love cloud endpoints - they speed up my development time and simplify my code significantly. Having said that, I'd really like to see some clarification from google. Are endpoints intended to be high performance? I haven't once seen mentioned in any google documentation that endpoints are low latency? I've often been waiting 5-20 seconds for calls such as /_ah/api/discovery/ v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fidpp=0. even on apps that have little traffic, tiny payloads and no rpc calls. One of the new systems i'm building is using endpoints but i'll have to switch away from endpoints ASAP if I can't get some reassurance. Also I don't have time to wait a couple of months to see if they get faster. I'd also be interested to know how efficient python / go / java / php endpoints are at encoding decoding different sized payloads with json or protobuff protocols. (Will probably have to generate these statistics myself present some graphs etc - although I'm assuming google would have already performance tested their own product?) cheers On Sunday, 25 May 2014 08:29:48 UTC+12, Diego Duclos wrote: I've done some (non extensive) tests on google appengine, and my response times vary from anywhere between 100ms and 5000ms when directly sending http requests to a cloud endpoints. Regardless of the actual response time, the google cloud console always shows a processing time of around 50ms, which, while also somewhat long-ish, is much more reasonable. For the 100ms requests, I can safely know that the other 50ms are just regular latency, but I have no idea where the cloud endpoint could be spending 4.5 seconds at, and the logs show nothing useful at all. Does anyone have some guidance for me regarding to this ? 5 seconds is unacceptable slow and makes them completely unusable. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Why are cloud endpoints so slow ?
also might be worth noting I'm using CORS on multiple app engine modules etc. perhaps it's something to do with preflight requests? http://monsur.hossa.in/2012/09/07/thoughts-on-the-cors-preflight-cache.html On Sunday, 25 May 2014 20:53:15 UTC+12, Robert King wrote: Don't get me wrong - I absolutely love cloud endpoints - they speed up my development time and simplify my code significantly. Having said that, I'd really like to see some clarification from google. Are endpoints intended to be high performance? I haven't once seen mentioned in any google documentation that endpoints are low latency? I've often been waiting 5-20 seconds for calls such as /_ah/api/discovery/ v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fidpp=0. even on apps that have little traffic, tiny payloads and no rpc calls. One of the new systems i'm building is using endpoints but i'll have to switch away from endpoints ASAP if I can't get some reassurance. Also I don't have time to wait a couple of months to see if they get faster. I'd also be interested to know how efficient python / go / java / php endpoints are at encoding decoding different sized payloads with json or protobuff protocols. (Will probably have to generate these statistics myself present some graphs etc - although I'm assuming google would have already performance tested their own product?) cheers On Sunday, 25 May 2014 08:29:48 UTC+12, Diego Duclos wrote: I've done some (non extensive) tests on google appengine, and my response times vary from anywhere between 100ms and 5000ms when directly sending http requests to a cloud endpoints. Regardless of the actual response time, the google cloud console always shows a processing time of around 50ms, which, while also somewhat long-ish, is much more reasonable. For the 100ms requests, I can safely know that the other 50ms are just regular latency, but I have no idea where the cloud endpoint could be spending 4.5 seconds at, and the logs show nothing useful at all. Does anyone have some guidance for me regarding to this ? 5 seconds is unacceptable slow and makes them completely unusable. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Service error from AppEngine
How to fix this error? It seem that occured somtime from FilterChain. java.lang.NullPointerException at org.apache.jsp.index_jsp._jspService(index_jsp.java:65) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:327) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) at com.google.apphosting.runtime.jetty.ResourceFileServlet.serveWelcomeFileAsForward(ResourceFileServlet.java:342) at com.google.apphosting.runtime.jetty.ResourceFileServlet.maybeServeWelcomeFile(ResourceFileServlet.java:281) at com.google.apphosting.runtime.jetty.ResourceFileServlet.doGet(ResourceFileServlet.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at ...dFilter.doFilter(Unknown Source) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:266) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:146) at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:446) at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:437) at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:444) at com.google.tracing.CurrentContext.runInContext(CurrentContext.java:188) at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308) at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300) at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:441) at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251) at java.lang.Thread.run(Thread.java:724) C 2014-05-24 17:23:38.899 Uncaught exception from servlet java.lang.NullPointerException at org.apache.jsp.index_jsp._jspService(index_jsp.java:65) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at
Re: [google-appengine] Re: Why are cloud endpoints so slow ?
The long delays sound like loading requests. Are they not specifically marked as such in the logs? Check the old legacy log system too. Loading requests are the achilles heel of appengine, especially for low-traffic apps. The only solution so far seems to be use Go. Jeff On Sun, May 25, 2014 at 2:00 AM, Robert King kingrobertk...@gmail.comwrote: also might be worth noting I'm using CORS on multiple app engine modules etc. perhaps it's something to do with preflight requests? http://monsur.hossa.in/2012/09/07/thoughts-on-the-cors-preflight-cache.html On Sunday, 25 May 2014 20:53:15 UTC+12, Robert King wrote: Don't get me wrong - I absolutely love cloud endpoints - they speed up my development time and simplify my code significantly. Having said that, I'd really like to see some clarification from google. Are endpoints intended to be high performance? I haven't once seen mentioned in any google documentation that endpoints are low latency? I've often been waiting 5-20 seconds for calls such as /_ah/api/discovery/ v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fidpp=0. even on apps that have little traffic, tiny payloads and no rpc calls. One of the new systems i'm building is using endpoints but i'll have to switch away from endpoints ASAP if I can't get some reassurance. Also I don't have time to wait a couple of months to see if they get faster. I'd also be interested to know how efficient python / go / java / php endpoints are at encoding decoding different sized payloads with json or protobuff protocols. (Will probably have to generate these statistics myself present some graphs etc - although I'm assuming google would have already performance tested their own product?) cheers On Sunday, 25 May 2014 08:29:48 UTC+12, Diego Duclos wrote: I've done some (non extensive) tests on google appengine, and my response times vary from anywhere between 100ms and 5000ms when directly sending http requests to a cloud endpoints. Regardless of the actual response time, the google cloud console always shows a processing time of around 50ms, which, while also somewhat long-ish, is much more reasonable. For the 100ms requests, I can safely know that the other 50ms are just regular latency, but I have no idea where the cloud endpoint could be spending 4.5 seconds at, and the logs show nothing useful at all. Does anyone have some guidance for me regarding to this ? 5 seconds is unacceptable slow and makes them completely unusable. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: Why are cloud endpoints so slow ?
These are not loading requests unfortunatly, The first request was ignored here, that one usually takes around 10 seconds (That's with Go, funnily enough) On Sun, May 25, 2014 at 7:51 PM, Jeff Schnitzer j...@infohazard.org wrote: The long delays sound like loading requests. Are they not specifically marked as such in the logs? Check the old legacy log system too. Loading requests are the achilles heel of appengine, especially for low-traffic apps. The only solution so far seems to be use Go. Jeff On Sun, May 25, 2014 at 2:00 AM, Robert King kingrobertk...@gmail.comwrote: also might be worth noting I'm using CORS on multiple app engine modules etc. perhaps it's something to do with preflight requests? http://monsur.hossa.in/2012/09/07/thoughts-on-the-cors-preflight-cache.html On Sunday, 25 May 2014 20:53:15 UTC+12, Robert King wrote: Don't get me wrong - I absolutely love cloud endpoints - they speed up my development time and simplify my code significantly. Having said that, I'd really like to see some clarification from google. Are endpoints intended to be high performance? I haven't once seen mentioned in any google documentation that endpoints are low latency? I've often been waiting 5-20 seconds for calls such as /_ah/api/discovery/ v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fidpp=0. even on apps that have little traffic, tiny payloads and no rpc calls. One of the new systems i'm building is using endpoints but i'll have to switch away from endpoints ASAP if I can't get some reassurance. Also I don't have time to wait a couple of months to see if they get faster. I'd also be interested to know how efficient python / go / java / php endpoints are at encoding decoding different sized payloads with json or protobuff protocols. (Will probably have to generate these statistics myself present some graphs etc - although I'm assuming google would have already performance tested their own product?) cheers On Sunday, 25 May 2014 08:29:48 UTC+12, Diego Duclos wrote: I've done some (non extensive) tests on google appengine, and my response times vary from anywhere between 100ms and 5000ms when directly sending http requests to a cloud endpoints. Regardless of the actual response time, the google cloud console always shows a processing time of around 50ms, which, while also somewhat long-ish, is much more reasonable. For the 100ms requests, I can safely know that the other 50ms are just regular latency, but I have no idea where the cloud endpoint could be spending 4.5 seconds at, and the logs show nothing useful at all. Does anyone have some guidance for me regarding to this ? 5 seconds is unacceptable slow and makes them completely unusable. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
