Hi, you are right.
Each entity contains the kind (model) name and property name, so dose the index.
So longer name will cost more cpu time.

You can use the name parameter to reduce the size:

class nDelta(db.Model):
    delta = db.FloatProperty(required=True, name='i')

2010/2/7 Eli Jones <[email protected]>:
> My bad... I forgot that FloatProperty and IntegerProperty values have a
> fixed size in the datastore..
> ..the only feasible place you would expect an increase in db.put()
> performance would be with StringProperty values...
> In my case, putting a bunch of Model.n entities with n.i = 1.0 is no
> different than putting a bunch with n.i = 100000000000000000.0
> Now, if it was a StringProperty with a bunch = "a" versus a bunch =
> "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", one might expect different
> db.put() performance.
> Or... again... this is what I'm beginning to learn.
> On Sat, Feb 6, 2010 at 4:09 PM, Eli Jones <[email protected]> wrote:
>>
>> Here is some information that I believe others might find useful.
>> I've been doing some more statistics on db.put() to the datastore.
>> I have two models:
>> class n(db.Model):
>>     i= db.FloatProperty(required=True)
>> class nDelta(db.Model):
>>     delta = db.FloatProperty(required=True)
>>
>> If I db.put(meList) to the datastore where meList is 100 entities,  get
>> these stats.
>>
>>                api_cpu_ms        ms
>> Model.n:         7800          ~1000
>> Model.nDelta:    9702          ~2500
>>
>> so... the longer names for nDelta,delta increase api_cpu_ms slightly...
>> but really blow up the clock time taken to do the put.
>>  24% more api_cpu_ms
>> 150% more time
>> If you're going to be putting a lot of entities from time to time..
>> tighten up the Model and Property names for faster putting.
>> Also, the actual put for Model.n was putting in much larger float values
>> than the put for Model.nDelta (nDelta had values between .01 and .99 while
>> Model.n.i had values ranging from 100 to 4*10^18)
>> .. so I would imagine if I put in the exact same values for n and nDelta..
>> Model.n would've put much faster.
>> Based on the len of the Model names plus property names (2 versus 11)...
>> one might expect Model.nDelta to take 450% more time to put when putting
>> equivalent FloatProperties..  that seems like a little much..
>> Suppose I shall test and see what really happens.
>
> --
> 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.

Reply via email to