For the legitimacy part, currently this is what I could achieve the best to
get my goal in my robot. I had to do this to make the robot memorise the
last options for a specific user.

The robot is already working since long time, but I am enhancing it to cope
with more users. It is [email protected]

If I tried to do the query from outside the BlipSubmitted,  the retrieved
data won't be reconginsed by the BlipSubmitted function. I tried to retrieve
the data on Robot Added, it doesn't work for some reason.

So the point of fetching 50 at a time is to remember the user's language for
an average of 24 -/+ hours.

2009/12/16 Dragon Silicon <[email protected]>

> Hi there,
>
> First of all, these error messages are a bit misleading: the used CPU upper
> limit has been lifted, so other than seeing these error messages, your
> application won't be infected. You might, possibly, reach the free quotas at
> some point, though.
> Secondly, I have doubts about the legitimacy for requesting 50 objects from
> the datastore for every BlipSubmitted. I think either your scheme, or your
> level of abstraction is currently flawed; a bit more detailed use case /
> description would allow me for sharing more detailed optimization
> techniques,.
>
> With that said, there are 2 quick&dirty workarounds:
> -global objects in appengine are persistent if served from the same
> machine; this means, you can fill up a list with the would-be requested
> objects, and use that at the next event;
> -Check out the Memcache 
> API<http://code.google.com/appengine/docs/python/memcache/overview.html>for 
> in-memory object persistence -these caching techniques could reduce
> datastore pressure tenfold, if applied corretly.
>
> -SDr
>
> On Wed, Dec 16, 2009 at 3:13 PM, [email protected] <
> [email protected]> wrote:
>
>> Since my last topic here where I asked about the best way to store and
>> retrieve data to/from datastore, I have done it, and using GQL I limit
>> the query to last 50 and fetch them. Now it worked for some time util
>> I started getting errors stating that "This URI uses a high amount of
>> CPU and should be optimised"
>>
>> The problem is that I have to do the query on BlibSubmitted function.
>> The error is for the url: /_wave/robot/jsonrpc
>>
>> How can I really optimise this and avoid getting such errors?
>>
>> Thanks
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "Google Wave API" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<google-wave-api%[email protected]>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/google-wave-api?hl=en.
>>
>>
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Wave API" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-wave-api%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-wave-api?hl=en.
>



-- 
Anglia Ruskin University
Bishop Hall Lane
Chelmsford
Essex UK
CM1 1SQ
Mob.No.:(+44)77 84 11 50 97

--

You received this message because you are subscribed to the Google Groups 
"Google Wave API" 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-wave-api?hl=en.


Reply via email to