Vinny thanks for the great Tip! Oh I thought if you used the datastore it
counted against your hours, but if you used memcache it did not, my
mistake. Again, thanks for the help to make my program more efficient!
-Victor
--
You received this message because you are subscribed to the Google Gro
On Thursday, March 7, 2013 5:29:12 PM UTC-6, victo...@gmail.com wrote:
>
> ...was wondering to store it all in memcache and non in the datastore to
> avoid front end instance hours...
Using either memcache or the datastore will incur instance hours, so I'm
not sure what you're trying to avoi
Thanks for all the replies. Yes, the reason I ask is because all the data I
aniticapte will be about 500mb big and was wondering to store it all in
memcache and non in the datastore to avoid front end instance hours, but it
seems as this is not a good approach since it is unreliable.
--
You r
On Thursday, March 7, 2013 2:38:39 PM UTC-6, Chad Vincent wrote:
>
> Or if you like, you could use Objectify which manages the Memcache as a
> Datastore cache automatically...
There are many data storage abstraction layers and frameworks available for
Java and Python on GAE, of which Objectify
On Thursday, March 7, 2013 1:13:35 PM UTC-6, Vinny P wrote:
> The smartest thing to do is to simply put everything into memcache, and
> when you need the object, pull it out. If the pull fails, then query the
> datastore/cloud sql.
>
Or if you like, you could use Objectify which manages the Mem
Nobody knows except maybe Google, and I doubt even they know.
The reason is that memcache exists in the memory of the particular machine
your application is on (as opposed to the datastore/cloud sql, which can
exist on another machine or span multiple machines). This means that
memcache is blaz
