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.
I'm happy to hear explanations. I didn't change the code I just did an
update withouth changing version.
-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of nickmilon
Sent: Friday, May 13, 2011 2:58 PM
To: Google App Engine
Su
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
Hmmm... The only possible explanation is that Greg just wanted to shut me up
about instances and python, so he hacked the dashboard to lie when I
upgraded my code next...
(When there is no plausible explanation propose an implausible one)
-Original Message-
From: google-appengine@googleg
10 matches
Mail list logo
