@ Gerald, You may end up loading a 32mb file from the blobstore. Just use
multiple page entities for a single article entity.
@ Keakon, Those reasons don't apply, seems you misunderstood the pattern,
feel free to ask for more details.
--
You received this message because you are subscribed to
At least your within the new daily limit of 28hrs for the free instance!
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/WAxArNusrP0J.
To post to
At least you're within the new limit of 28hrs for a free instance -
http://googleappengine.blogspot.com/2011/09/few-adjustments-to-app-engines-upcoming.html
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web
But part of what you are getting with App Engine is the ability to scale
when you need to without having to completely re-architect
That's kind of ironic. To start with app engine YOU HAVE to completely
re-architect the app to accommodate App Engine (compared to every other
platform/framework
I got 50k Datastore Reads on Sep. 8 again, but CPU time just increased from
0.3 to 0.35.
The memcache hit ratio also increased from 55% to 56%, but not scale
enough.
I think the only way I can keep it under 50k is prevent all spiders.
I also have doubt about the instance hours. I have set the max
希望你的努力有效[?]
2011/9/10 keakon lolicon kea...@gmail.com
I got 50k Datastore Reads on Sep. 8 again, but CPU time just increased from
0.3 to 0.35.
The memcache hit ratio also increased from 55% to 56%, but not scale
enough.
I think the only way I can keep it under 50k is prevent all spiders.
Hmhm, tell us when you have successfully set the max idle instances to 0.
2011/9/10 keakon lolicon kea...@gmail.com
I got 50k Datastore Reads on Sep. 8 again, but CPU time just increased from
0.3 to 0.35.
The memcache hit ratio also increased from 55% to 56%, but not scale
enough.
I think
IIRC Max entity size is 1MB?
I'd be surprise if all the entities loaded by your page adds up to that kind
of size
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
This forum thread is only 20kb, add some meta data and you are at 30kb max.
For an article with 20 comments.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Hi all,
I have 3 reasons why can't do that:
1. There dose be some articles with more than 1000 comments in my blog.
2. It's an open source project, I can't assume other users won't hit the
limitation.
3. I need provide feeds for the latest comments across all articles.
I'll keep watching on my
You can trying caching the comments per article into a blobstore. I believe
there is API available now to write to the blobstore, but you will have to
wait until the blobstore API is available to non-paid apps.
I'd think the latest comments feed should be able to fit within the
memcache.
--
I've thought of caching to the blobstore too, for stuff that will include a
lot of entities and don't change a lot.
Has anyone tried this, is it plausible?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web
Hi all,
I just did some optimization these days, now the Datastore Reads operations
per day drops from 70k to less than 40k.
I achieved this by 2 ways:
1. Hooking every datastore operation, logging the requests which fetched
more than 5 entities, then checked each of them if I forgot to
I didn't merge entities together because it will make my code hard to
understand and maintain. The max entity size also prevented me to do this.
You keep the entities because you will need them to do the queries, in order
to build a page entity. A 'page' entity is a cache object which you
One thing you could try is to store all your tags serialized into one entity
instead of 50 separate entities.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Thanks, Gerald. I would have a try.
But I'm not only fetch tags, there are many kinds of entities in my blog.
Say I have a article with 20 comments, I need fetch 1 article + 2 nearby
articles + 5 relative articles + 20 comments + 20 comment arthurs = 47
entities.
Maybe I need to log all the
Hello Keakon,
Very nice blog, cool design.
Follow up by Gerard. Create a new entity named ArticlePage. This entity has
all the information to display a single page of an article. Depending on the
number of comments, an article can have more than one ArticlePage.
Only cache the ArticlePage
Hi Greg, thanks very much for your informative reply.
I didn't intend to bash App Engine in that post, just to speculate
that the underlying issue might lay in the inherent costs of running
the architecture, rather than (say) some cynical, ill-advised business
decision to squeeze the customers
On Sep 2, 2:08 am, keakon lolicon kea...@gmail.com wrote:
I wish I was the one who made a wrong decision.
Ouch.
It is sad that the billing changes seem to price a ton of
international customers out of the market.
I wonder if recent events mean that the App Engine model (for lack of
a more
Hi Sasha,
It is indeed more expensive to run App Engine than the alternatives you
mentioned for a few reasons:
- We have a lot of infrastructure built out around the core machines that we
don't charge for specifically but are included in the price of what you pay
for (the request queue, the
Gregory,
I just want to let you guys know that I love app engine and my app
does not need major scalability, and never will. However I like app
engine or reasons OTHER than scalability. I like the ease of use,
essentially the PAaS aspect. I love the gae apis available. I love
the dashboard. I
21 matches
Mail list logo
