Oh, and: 756 - one StringListProperty with 1 element with 490 characters.
So each of the three trials had just one property was under 800 mcycles regardless of the size of the property. On Oct 15, 9:17 pm, Josh Heitzman <[EMAIL PROTECTED]> wrote: > As we didn't see anyone from the GAE team confirm or deny that the > excessive mcycle consumption for doing an entity update was due to the > number of properties on the entity (see this > threadhttp://groups.google.com/group/google-appengine/browse_thread/thread/... > ) I decided to do a little experiment. > > Follows are the average mcycle consumptions (on GAE not locally) to > update 4 different types of entities. Each entity has no parent and > or children (i.e. its the one and only entity in its group). There > was no contention as these entities were created solely for this test. > > 754 - one IntegerProperty > 864 - One each of IntegerProperty, DateTimeProperty, FloatProperty, > and StringProperty > 718 - one StringListProperty with no elements > 2141 - one StringListProperty with 40 elements each with 14 > characters. > > Has anyone else done a similar experiment? > > If so did you get similar results? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
