>From docs (http://code.google.com/appengine/docs/java/datastore/ relationships.html)
---------------------------------------------------------------------------------------------------------------- "Tip: In some cases you may find it necessary to model an owned relationship as if it is unowned. This is because all objects involved in an owned relationship are automatically placed in the same entity group, and an entity group can only support 1 to 10 writes per second. So for example if a parent object is receiving .75 writes per second and a child object is receiving .75 writes per second, it may make sense to model this relationship as unowned so that both parent and child reside in their own, independent entity groups." ---------------------------------------------------------------------------------------------------------------- Does it mean that GAE does not work for such applications if they need to insert more records per seconds? Example, on peak hour usage, it is very reasonable for application to insert 20 to 50 records per seconds for an entity group. If we require both transaction and peak hour insertion, I think it is hard to work around from application level. Example, to support transaction, the entities must be in the same entity group. But from the same entity group, GAE can only support 1 to 10 writes per seconds. Is this true? Regards Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
