Same Problem here.
--
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 google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
Hi John
I'm afraid I cannot offer any specific suggestions, but I it may be
worth looking at the Objectify persistence framework, one of its
primary goals was to reduce start up time. If nothing else, trawling
the documentation may give you some valuable clues
On Aug 4, 2:57 am, John
Looking at the comment in
org.datanucleus.store.appengine.DatastoreManager.getDatastoreClass()
could lead one to think, there are race conditions related to
initializing the meta-data of persistent classes. Since your problem
occurs only from time to time, it could point to the same direction.
Are you experiencing into the new functionality of the SDK, which is
emulating the eventual consistency of a High-replication datastore? This is
turned on by default in the newest SDKs - see this post for more info -
https://groups.google.com/forum/#!topic/objectify-appengine/ECNbSVgEcSQ
--
Hello,
I want to diplay my images in a lightbox like shadowbox or clearbox.
These scripts work fine with a static image file, but not with dynamic
serving resource like a Servlet or ImageService, so that the frame in
wich the image is displayed doesn't fit the image.
Does someone has encountered
Hi Moishe,
I have a question regarding the channel
api.
When i establish a channel and if i refresh the current page , whether
the post to /_ah/channel/disconnected/ will be sent and then the
channel will be recreated again with a post to /_ah/channel/
connected/?
Absolutely love the prospective search feature for event processing. when
will this feature be available for the java version of the app engine? It
will make the platform so much more powerful! Thanks!
--
You received this message because you are subscribed to the Google Groups
Google App
this is a really strange issue, and only affecting the production web
admin-console.
The requests are logged, but any custom logging (either via logging libs or
even with simple System.out.println) does not appear in the logfiles
anymore.
What is happening ? Nobody else complained yet. Is it
Do you normally see the DeadlineExceededException? If not then perhaps you
are running into this dead-lock issue :
http://code.google.com/p/googleappengine/issues/detail?id=5384
Try turning off thread-safe mode - that fixed the problem for me while I
wait for a proper fix for multi threaded
Eduardo, that doesn't seem to be a valid app ID. The app ID is what you use
in app.yaml or appengine-web.xml to deploy.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Quick question: do you use the datastore as a queue? This is a known
antipattern if you have a relatively high throughput.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Why isn't denormalization a real option? A lot of companies denormalize with
great success, including Google.
The thing about joins is this: they have to happen at some point in memory.
Datastore or local instance.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com |
Hi,
I saw another post where a user was asking a similar question to this, but
he didn't seem to have quite the same scale of discrepancy as me:-
I have the following datastore statistics:
Total number of entities Size of all entities
39,307 12 MBytes
And here
Because if you have denormalized data, then record updates can become
enormous. If someones address is denormalized into 1000 contact records,
then when the user updates their address the system has to go out to all of
the contact records and update them as well. And this gets multiplied by
William,
Could you explain how the update can be enormous with demoralized table? My
understanding is a flat table is easier to update that normalized one.
Thanks.
On Aug 5, 2011 1:36 PM, Ikai Lan (Google) ika...@google.com wrote:
Why isn't denormalization a real option? A lot of companies
I was trying to explain that with...
If someones address is denormalized into 1000 contact records, then when the
user updates their address the system has to go out to all of the contact
records and update them as well. And this gets multiplied by every complex
relationship that exists in
William,
You might want to go over this
http://static.googleusercontent.com/external_content/untrusted_dlcp/labs.google.com/en/us/papers/mapreduce-osdi04.pdf,
and come back again with any questions. Ikai and possibly others were
trying to convey to you that bigtable approach is more scalable
I didn't mean to suggest that.
Yes, a fanout is potentially bad, but the problem with the normalized
approach is that you equally optimize for reads and writes. In the address
book example, I update my address book about 1 time every 3 years. I read my
address book 20 times a day. I think it's
As far as managing complex data relationships, I don't think such a set of
practices exists. What I can and should do (once I get some time) is publish
some case studies about how we have persisted data in some cases. True,
denormalizing data often requires you to think a little bit, but that's
Hi Simon,
That was the issue - the HRD was on !
I turned it off and now it works fine !
Many thanks for the help !
Daniel
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
after even request logs having trouble (massive delays), now everything
seems to be fine again.
really strange.
--
Roberto
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
I am not sure what you meant by fan out and fan in but I agree with you that in
relational world, data are more consistent as they are stored and enforced by
constraints etc. but demoralized form does not requires joins, which makes them
more scalable as less overhead.
If one high level entity
On Fri, Aug 5, 2011 at 11:45 AM, William Levesque
billleves...@gmail.com wrote:
But is Google's position that all data should be denormalized?
I don't think anyone would say that. I wrote up my thoughts around
this subject here:
Hi all,
I'm very happy to announce the *final release of Gaelyk 1.0*, the
lightweight Groovy http://groovy.codehaus.org toolkit for Google App
Engine!
It took some time to get to 1.0, but it's now here, with the key feature
I've been missing since the beginning of the project, in particular the
Sorry, I gave you the Marketplace appId. The Google App Engine appId is
share-gmail.contacts.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
John,
I don't see the DeadlineExceededException for hours (10-12 hours), then
suddenly, I only see DeadlineExceededException on every single query I do on
a specific Entity Kind (but not in others) during hours (6-8 hours). It is
like a very repetitive pattern.
Yes, I put
Guillaume, congrats to Gaelyk and all its developers! Glad to hear
it's now version 1.0!
I'm currently developing admin console for my app, so far so good :)
On Aug 6, 10:00 am, Guillaume Laforge glafo...@gmail.com wrote:
Hi all,
I'm very happy to announce the *final release of Gaelyk 1.0*,
27 matches
Mail list logo
