Hi All,

My app uses JDO with the DataStore. When writing an Entity with ~100 
children a request could take somewhere between 3-10 seconds realtime and 
~80331cpu_ms 
~78231api_cpu_ms. 
Can these numbers be improved for writes of this size? Is there a good 
chance my requests will deadline?

After reading the docs and watching the IO sessions, I got the following 
ideas for improving performance:
* Using the low level api with setMulti() should clump all the writes into a 
single RPC. I'm guessing PersistenceManager isn't doing that for us with 
ArrayList<> child objects? 
* Try using the Async API
* I couldn't find any obvious way of improving JDO write speeds

I'd really appreciate some direction so I don't waste my time trying a 
thousand solutions. Any advice would be awesome!
Thanks,
Chad 
P.S. My data structure is as follows (abbreviated code):
Parent{
String key; // String key
ArrayList<GameData> gameData;
ArrayList<UserData> userData;
}
GameData{
private Key key; private int itemType;
private int item; 
private float ...; 
private float ...;
private int ...   
private int ...;
private int ...;
private long ...;
private int ...;
}
UserData{
@PrimaryKey
@Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
private Key key;
private int ...;
private String ...; 
private long ...; private boolean ...;
}

-- 
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 
https://groups.google.com/d/msg/google-appengine-java/-/dXJiA5r7OfYJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to