Thanks for all the answers. I've been trying to solve this problem by
reducing the scale of my data, and will get the result two days later.
Thanks again, for the suggestions, and for the kink ones who gave me advice!
Chun
2011/3/18 branflake2267
> I had this happen to. What I did is setup a ser
I had this happen to. What I did is setup a servlet to virtually serve them
from the blob store, by using a web.xml to serve them dynamically
or virtually. I had no problem with latency.
http://demogaemultifileblobupload.appspot.com/ - my demo doing it. You can
find source code on my site to ho
Hi,
the big difference between memcache and "loading to memory" as you say
is that the memcache is automatically replicated for you across the
jvm automatically started by gae.
You can load yourself in memory by (for example) using a singleton as
the anchor point for a data structure (probably a
Thanks for your advice. But I want to know the difference between loading
the records into the main memory and loading the records into the memory
cache. An other question is, both of the two approaches will consume a lot
of time, but the performance of the former is still questionable.
Expecting y
If your app is gwt-based, you can reduce the size of your resources by
reducing the number of permutations.
Gwt compiles one specific final resource package for each permutation (e.g:
5 browsers x 3 locales > 15 permutations).
This might lead to very heavy resources. See
either http://code.googl
Hi,
In order to achieve your goal is the quota limit cannot be changed,
may I suggest though that you still update your file to the datastore
to serve them back to your clients.
You would not serve them from datastore but upload them into memcache
(all at startup or 1 by 1 on 1st use) and serve t
Hi,
The restrictions around your deployed application can be seen at
http://code.google.com/appengine/docs/java/runtime.html
The maximum size of your deployed WAR has to be 150MB, as far as I'm aware
it's not a quota which can be increased.
Cheers,
Simon
--
You received this message because
