Hi Christian, thanks for your informative reply. You were right, I do use URL and A quite a lot, and most of LOGs come from that two helpers. I also managed to completely turn off logging by modifying logging.conf.
Interesting, today my website is performing much much better - without any changes to the code. I am not getting deadline exceptions any more. I guess this has something to do with GAE performance in general - dont know. Im certain that some (mem)caching will additionally boost the performance. If I may; would you be so kind and list some of the tasks one should do, to optimize project for serving on production GAE? Some common steps like "use this, instead of this", "set foo to bar", "never do this", etc. I hope this makes sense :) Cheers, Damien On Oct 24, 11:47 pm, howesc <[email protected]> wrote: > Damjan, > > i use GAE heavily, here's what i can say based on what i see: > - each call to URL() puts at least one message in the debug log. so > whatever you are doing has lots of calls to URL() in it. > - logging can be affected by logging.conf, but i've never successfully > suppressed logs i didn't care about and got logs i liked. > - i don't get random deadline exceeded messages on GAE, i do get them when > i write bad code. one such mistake i made was running a query in a model > file (db.py) that returned lots of rows. > > if you can provide a simple model + controller that exhibits the problem we > can help troubleshoot. > > christian
