Jeff, thanks for the heads up on that issue; opened
http://code.google.com/p/googleappengine/issues/detail?id=814 to
publicly track it.
Josh
On Oct 24, 11:56 am, Jeff S <[EMAIL PROTECTED]> wrote:
> It sounds like davekor's app might not need to be fixed further if
> your app is not using very much runtime CPU (in code outside of the
> datastore). The CPU megacycles for datastore operations do not
> currently count against the per-request ("High CPU Request") limits.
> We're working on ways to make this clearer in the Admin Console.
>
> Happy coding,
>
> Jeff
>
> On Oct 24, 4:06 am, Josh Heitzman <[EMAIL PROTECTED]> wrote:
>
> > If you can't reduce the number of entities, then all you have left is
> > to reduce the number of indexed fields on the entities and the number
> > of elements in any list fields on the entities. That said you can't
> > put two entities with only a single non-indexed property each in less
> > then 1000 mcycles.
> > Seehttp://code.google.com/p/googleappengine/issues/detail?id=786
>
> > On Oct 23, 6:57 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > My application get a lot of high-CPU usage warnings on the production
> > > server. I have spent the past few weeks profiling and optimizing my
> > > production code as suggested.
>
> > > From profiler data, I know that 99% of processor time is spent in
> > > Model.put or db.put. As a result I have been aggressively eliminating
> > > unnecessary or duplicate write operations. For instance in my most
> > > processor intensive http request, I have cut down the number of
> > > entities I update from 5 to a varying number between 0 and 3 depending
> > > on what absolutely must be updated. I also batch writes by using
> > > db.put() instead of separately calling Model.put(). As a result, I
> > > have cut the number of mcycles down from 7000+ to an average of around
> > > 2000 mcycles.
>
> > > However, I still get high cpu warnings on one http request, because it
> > > absolutely needs to update 3 separate entities (two node entities in a
> > > directed graph, and a sharded counter entity). So my question is, what
> > > else can I do to further optimize this specific section of code?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
