Memcache is shared across instances, automatically it is available as
a service you do not have to load it just. User it straight away to
store or access object in memory.
Thanks,
Yogesh
On May 22, 9:37 pm, Rahul wrote:
> Chau,
>
> Thanks for pointing to the link. I did go through the link and
This sounds a lot like the sharded counter scenario. I think they came up
with a committing to datastore strategy that worked well.
On another hand, you can always queue a task and let the task queue persist
the preferences when it gets around to it.
On Mon, May 24, 2010 at 11:16, Rahul wrote:
Ok. Let me explain the complete scenario.
Suppose I have lot of preference on my page which are stored in the
database. Now i have multiple options,
1. Load all the preference in Hashmap in a servlet and mark that
servlet as Load-on-startup to 0 and then use the hashmap cache when a
new user visit
Chau,
I have already tried various solutions out of those mentioned above,
including "b) request Google to load your app before start dispatch
request to that instance " but it is still slow, My exact question is
when to put the data in cache.
Thanks,
Rahul
On May 24, 4:49 am, Chau Huynh wrote
Tristan,
I do understand what you are saying but my question is there exactly
do we need to put data in memcache. If i put it in a servlet and load
that servlet with load-on-startup parameter, then does it remain in
cache for the entire period as I guess, load-on-startup servlet is
loaded every ti
Hi Rahul,
About loading request/performance, there're lots of discussions that you can
find in the groups, please just try google it.
Here are some notes based on reading those.
Latency causes by
1- time to start new JVM
2- time to load your application
To reduce load time by 1) others star requ
The way you load the memcache, you just put data in it. It is
automatically shared between all JVMs and you don't have to do
anything special. As to when to load it up. Say you have some
preferences stored in the datastore. You should put those preferences
into the memcache and always check the mem
Chau,
Thanks for pointing to the link. I did go through the link and i
think, what i thought was right.
Also i was going through the following point in the section you
provided : "How can I speed up loading requests? " and the second
point mentioned is "Share expensive initialization between JVMs.
