Thanks for the tips, Brandon!
A quick question: those "scratchpad" datastores are python dicts, right?
We need to be aware that the dicts are not coordinated across instances so
they may have stale data (which might be ok depending on the app). Just
want to make sure I understand your sugges
On Saturday, May 14, 2011 8:54:54 PM UTC+1, Robert Kluin wrote:
>
> If the data doesn't get updated, using the blobstore might be a good
> idea. As I recall, you can't update a blob. So if the data changes
> it may not be the best idea. Of course, it really all depends on the
> app / usage.
If the data doesn't get updated, using the blobstore might be a good
idea. As I recall, you can't update a blob. So if the data changes
it may not be the best idea. Of course, it really all depends on the
app / usage.
I store serialized dicts / lists in text / blob properties quite
often. It w
.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Tim
Sent: Saturday, May 14, 2011 1:42 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: 1.5 improvements Make me less scared of
Pricing
I suspected that might be the case, but if I have a few minutes to spa
I suspected that might be the case, but if I have a few minutes to spare
sometime I might try it out.
My startup and servicing costs is pretty minimal - I've got a
one-page-webapp and most of my calls are just AJAX calls to load and update
data, so it's typically just object to JSON and back ag
Hey Tim,
That will (probably) just stop your module being cached, making it
respond more slowly to requests, increasing the number of instances
needed to service concurrent requests. I think you're still better
off to try to make instance startup and request servicing as efficient
as possible.
App Engine
Subject: [google-appengine] Re: 1.5 improvements Make me less scared of
Pricing
@Brandon Wirtz
All this can't be explained by you upgrading to 1.5 as @Stephen writes.
@Vinuth Madinur +1 for all your points especially minimum granularity.
;-)
Nick Milon
On May 13, 4:28 pm, Tim wro
@Brandon Wirtz
All this can't be explained by you upgrading to 1.5 as @Stephen
writes.
@Vinuth Madinur +1 for all your points especially minimum
granularity.
;-)
Nick Milon
On May 13, 4:28 pm, Tim wrote:
> Currently all my python scripts use the script-or-module mechanism as
> recommended by t
Currently all my python scripts use the script-or-module mechanism as
recommended by the docs
application = webapp.WSGIApplication([('/somepage',
SomeHandler), ('/anotherpage', AnotherHandler)], debug=True)
# GAE will look for a main() with no args and, if found, caches this script
# so we sup
No doubt when I moved to HR my instances basically quit dying. With M/
S an idle instance would be killed off quickly, with HR they hang
around for days. At the time I was very happy about this. This was a
complaint in the past (how fast Google killed idle instances.) But now
I think the reverse
I'm not seeing any significant reduction in instances either. I did
notice that I got a lot more idle instances when I moved from MS to HR
datastore, for some reason - maybe they are starting to rationalise
this and haven't got to my instances yet.
Cheers
Greg.
--
You received this message becau
And it would be great to have different pricing for idle instance hours vs
active instance hours. Because my app is letting other apps execute, while
blocking a little memory.
On Fri, May 13, 2011 at 1:20 PM, Vinuth Madinur wrote:
> Plus:
>
> 1. 15 minutes minimum granularity.
> 2. Tiered Instan
Plus:
1. 15 minutes minimum granularity.
2. Tiered Instance pricing. My app consumes about 40 -80 MB, but I'll be
paying for 128 MB 0r 256 MB minimum.
3. It's not like they can't meter these or aren't metering these. They
already have the numbers. But they wont price things based on it, which
suck
@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of JH
Sent: Thursday, May 12, 2011 7:55 PM
To: Google App Engine
Subject: [google-appengine] Re: 1.5 improvements Make me less scared of
Pricing
Interesting, I saw no change to my # of instances with 1.5
On May 12, 9:29 pm, "Br
But still 6 instances for 13 QPS (2.22 x 6) sounds stupid to me if the
pricing will be instance based. A single regular class VPS can handle at
least like 30+ QPS.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, se
Interesting, I saw no change to my # of instances with 1.5
On May 12, 9:29 pm, "Brandon Wirtz" wrote:
> I am slow to upgrade because I like to know that things won't explode, but
> this graph shows how 1.5 reduced the number of instances I need compared to
> 1.4 (maybe 1.3) that I was running. U
16 matches
Mail list logo
