As I know, pre-allocate is nothing about performance, and use single put to save entities is faster than put each of them. ---------- keakon
2010/8/10 Jaroslav Záruba <[email protected]>: > Hello > Could someone tell me which approach is 'cheaper', please? > Let's have two entities... > - persistedBasket // already persisted entity, holds item IDs > - newItem // does not have ID yet > Should I put(newItem), pass its ID to persistedBasket and then > put(persistedBasket), or is it 'cheaper' to pre-allocate single ID for > newItem and then do put(persistedBasket, newItem)? > In other words, does it make sense to pre-allocate single ID to make single > put(item1, item2) instead of two consecutive put's? > Regards > JZ > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
