Google is a bit schizophrenic right now IMHO. Its pricing is enterprise, 
yet it still desires the startup developers' halo (appealing to their 
desire for high-productivity). So GAE product managers have been riding the 
backs of startup developers who chafe at the enterprise-level pricing while 
waiting for enterprise CIOs to lose their fear of GAE's PaaS lock-in. 
Recent lowering for SSL monthly costs (and posts by new GAE PMs) suggests 
some internal debate. You may or may not be in the final product's pricing 
schema. Unfortunately I believe these are the pains we suffer as a very 
intelligent set of engineers gain an understanding of value-added services 
(as opposed to Amazon who makes no mistakes re: providing value-added 
services). Remember: Google is a great adwords/adsense company trying to 
expand to value-added services. GAE is pretty new for them.

On Tuesday, October 9, 2012 10:40:42 AM UTC-7, James Gilliam wrote:
>
> The main point I am making is offsets are useless because reading all 
> records from 0 to offset costs the same as reading a a record from +offset. 
>  If GAE didn't charge for the records being skipped, it would be useful to 
> use offsets. I suspect the only reason they charge for skipping records is 
> because they cannot locate the nth record without reading them all.  This 
> suggests a defect in their design that has nothing to do with entity 
> database.
>
> I realize that getting GAE to fix this issue is impossible.  However, the 
> list of GAE issues continues to mount.  For example, not getting bounces on 
> mail has been an outstanding issue for three years even though the 
> documentation clearly says it is supported.  Another example is the 
> horrible cost for secure domains and offering a 'cheaper' alternative that 
> only works in limited situations.  I am just getting tired of the gae 
> issues and they clearly don't care.
>
> On Monday, October 8, 2012 11:07:45 AM UTC-7, James Gilliam wrote:
>>
>> I discovered that GAE charges you for skipping entities in Datastore with 
>> OFFSET.  So, if you want to retrieve 1 record at offset 10, you pay for 
>> reading 11.
>>
>> This makes OFFSET expensive and WORTHLESS ...
>>
>> Offset should never be mentioned in the documentation without a footnote 
>> that says you can't afford to use it.
>>
>> Kinda pissed about this.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/GTf2QGpKwXUJ.
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