Re: [google-appengine] Re: Bad news for GAE/Java from Google I/O

And it's possible to not use app engine at all, and then not have to worry about how fast your app starts. As a bonus, it's far cheaper as well! "Possible" is never a useful word to throw around here - it's possible to rewrite your java webapp in Go, it's possible to convince people they don't even

Re: [google-appengine] Re: Bad news for GAE/Java from Google I/O

Hi Matt, Thanks for some official word from Google - it was starting to turn into an echo chamber on Google's own product forum. That said, the solution still isn't satisfactory. Even a single 5 second wait at the wrong time is very, very bad. If I'm paying with a credit card, and my request ge

[google-appengine] Re: Bad news for GAE/Java from Google I/O

Very unfortunate, but it's been clear that GAE/J has been getting the short end of the stick for awhile. Given the heavy costs for doing anything 'heavy' on GAE/J, and the prevalence of new hosting providers that can give you a full 8 core VM for similar prices to GAE's incredibly underpowered

Re: [google-appengine] Re: Google App Engine 1.7.5 SDK now available!

points. > > If you want a VM or a comparison to EC2, you should really do it with > GCE, not App Engine. > > On Fri, Feb 15, 2013 at 9:10 PM, Ryan Chazen > > wrote: > > With the kind of issues AppEngine has - high prices, random bad > performance, > >

Re: [google-appengine] Re: Google App Engine 1.7.5 SDK now available!

With the kind of issues AppEngine has - high prices, random bad performance, limited features (no sockets, etc), no support, java instance startup times, routing new requests to instances that haven't started yet, incredibly small VMs - I think the humour is probably on Google's side also. AppE

[google-appengine] Re: Cost of updating list property

Depends if those integers are indexed or not. Each index is a write op. However, an entity can only be 1mb big.. I think 1 million integers would be more than 1mb as appengine stores natively as strings... What you could try is to store the integers in multiple entities (say 1-1000 integers per

Re: [google-appengine] Re: Pagespeed increases load time and index

If you use all of GWT's client bundle options then you already have the effect (and more) of PageSpeed. Automatic image sprites, embedded resources, embedded css, etc. Running all of this through PageSpeed again is just wasting a lot of work to re-do what is already handled by GWT's compiler.

[google-appengine] Re: Memcache writer exception

Appstats persists the stats to memcache so that you don't use up pricey datastore writes on stats data. What's going on there is that the memcache write appears to be failing (?), and this is making it crash out. You are probably triggering a bug in appstats to cause this - ParseBlobUploadFilt

Re: [google-appengine] Simple Invoicing as Service

It's running off http://static-libs.appspot.com/ So looks like app-engine to me with a frontend On Sunday, January 6, 2013 12:53:25 PM UTC+2, alex wrote: > > I don't think so: > > "Powered by Industrial Strength Technologies including AppFog, Python, > MYSQL and running on HP OpenStack Cloud Pla

Re: [google-appengine] Understanding keys-only query costs

, Jan 5, 2013 at 4:53 PM, Johan Euphrosine wrote: > > > On Sat, Jan 5, 2013 at 5:21 AM, Ryan Chazen wrote: > >> >> Thanks Johan, but I don't think there is any real defect here - 'IN' does >> work as documented - it's just not very useful as curren

Re: [google-appengine] Understanding keys-only query costs

rform well, so it's just a bit out of place and I'm sure it has blindsided a lot of people so far. On Saturday, January 5, 2013 2:37:28 PM UTC+2, alex wrote: > > are you running this on dev or production server? > > > On Sat,

Re: [google-appengine] Understanding keys-only query costs

Ouch ouch, it's even worse than expected. I ran an query with an IN filter with the same value repeated. eg IN[0,0,0,0,0,0,0,0,0,0,0] - The query runs completely in serial doing an indep

Re: [google-appengine] Understanding keys-only query costs

why do you even have support for them if they don't work? Are there any plans on the horizon to make 'IN' queries work as in every other nosql database? On Saturday, January 5, 2013 12:49:34 AM UTC+2, Guido van Rossum wrote: > > On Fri, Jan 4, 2013 at 1:59 PM, Ryan Chazen &

Re: [google-appengine] Understanding keys-only query costs

ions using interactive appstats examples (click the Run button on > each slide). > http://proppy-appstats.appspot.com/#2 > > Hope that helps, and let me know if you experience anything different. > > > On Fri, Jan 4, 2013 at 1:12 PM, Ryan Chazen > > wrote: > >&

[google-appengine] Understanding keys-only query costs

Hi, Could anybody help me out with understand keys-only query costs? I've done the following tests: Fetch 2 items using a regular query (fully entity fetched) - (3 RPCs, cost=350, billed_ops=[DATASTORE_READ:5]) Fetch 2 items using a keys-only query, and then fetch the full item (cache miss) - (

Re: [google-appengine] Re: Jersey REST with List<> as a query parameter

dy by default if you use the standard @Attribute methods. On Fri, Jan 4, 2013 at 8:00 PM, ludovic Champenois wrote: > On 1/4/13 7:51 AM, Ryan Chazen wrote: > >> Is there any way to run unit tests on appengine directly instead of >> running them only on the dev server? >> >

[google-appengine] Re: Jersey REST with List<> as a query parameter

Is there any way to run unit tests on appengine directly instead of running them only on the dev server? At any rate, the error is not from the multiple query parameters, but rather (found from a Google search), that the addHeader method on AppEngine live does not accept nulls while the dev ser

[google-appengine] Re: Jersey REST with List<> as a query parameter

The stack trace from AppEngine is as follows: com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException: The RuntimeException could not be mapped to a response, re-throwing to the HTTP container java.lang.NullPointerException at org.mortbay.io.Portable.getBytes(Portabl

[google-appengine] Jersey REST with List<> as a query parameter

In JAX-RS, the following is valid: @GET @Produces(MediaType.APPLICATION_JSON) @Path("/test") public Response getTest(@QueryParam("ids") List ids) To call this, you could use /test?ids=1&ids=2&ids=3 This works correctly on the AppEngine dev server (jetty), but when deployed to Ap

[google-appengine] Datastore write costs

Hi - I find the following a bit confusing - is it correct? Using unindexed properties only: If I write 10 numbers in a list to the datastore, _ah/admin on the local dev server shows 10 write operations. If I write 10 numbers inside an embedded entity (or comma delimited), the local dev server s