I was curious about logging load, as well, so I ran a few small tests. It looks like it costs around 0.25 milliseconds per log call on the production server. Which is not free but is very cheap.
But I also noticed that the development server takes a dive if you log more than around 500 times in response to a single request. Haven't investigated why that might be but it did explain some puzzling hangs I had when debugging over-logged code. The production server has no such issues and happily logged as many as 10,000 times in a single request. The load time rose to around 0.4 milliseconds per log in this test, though. I was also duly chastised in the log entry for using so much CPU in a single request. I'm still puzzling over the CPU usage claims. This 10,000 log entries test seems to complete in around 0.786 seconds wall clock time (using Pythons time module to record start and end time of the request then taking the difference) but is charged 3948ms in CPU. Which seems odd. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
