It's probably that expensive. There are many surprises when using the datastore! I'd really like to get to grips with exactly what is causing what performance issues because it still feels a bit uncharted.
Possibilities: Check if this speeds up if you call it a number of times in a row. Your app might have to load. I'm finding that it unloads very quickly now - a few minutes, whereas it seemed to take up to 20 min before. I also feel like repeated calls of a similar kind seem to run faster. When I turn logging onto "Info" level, I see a few exceptions when some parts wake up, like queues. Those don't happen after the first call. How many 'columns' do your children have? Each of those have to be indexed. You can specify that the datastore ignores some columns for indexing. Do your children have list properties? If so, that expands the indexes a lot. Look at your data stats to see how much indexes are taking up compared to data, which should hint at how much the store is doing behind the scenes. Regards, Richard On Dec 17, 7:40 am, Brian Hayward <[email protected]> wrote: > Am I doing something wrong here? > > Parent class with an owned one-to-many relationship containing 30 > children. calling clear() on the collection and then makePersistent() > on the parent was: > > 1646ms 5065cpu_ms 4560api_cpu_ms > > Is it really this expensive? I have timing around the above two > steps, my logs reported that part alone as 1552ms. > > Thanks, > Brian -- 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.
