Hi,
With the cache enabled I get a huge performance gain. In total it
looks close to my handmade cache. And it is so easy to put in place...
The First request takes some time but subsequent are really quick.
The problem is that it only works only on localhost. When I deploy my
application I get a deadline error.
A regular request takes 13sec (I retrieve about 300 entities and
return a list, each entity contains about 4 fields). If I do the same
with the jdo cache I get to the limit of 30 seconds and my process
gets killed. So the cache takes a huge overhead (in contrary to my
homemade solution).
Could I be missing some configuration? Right now I put this:
<property name="datanucleus.cache.level2.type"
value="javax.cache"/>
<property name="datanucleus.cache.level2.cacheName"
value="javax.cache"/>
and the jar. No annotations, nothing else.
Thank you for any advice.
Toby
On Mar 8, 1:11 pm, datanucleus <[email protected]> wrote:
> > Do I understand right, that this L2 cache is doing exactly the same?
>
> Indeed, part of the JDO1/JDO2 and JPA2 specs.
>
> > Why is it not disabled by default (are there draw backs)?
>
> It *is* disabled by default in DataNucleus 1.x. It is enabled by
> default in DataNucleus 2.x (which GAE/J doesn't support still).
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
