[ZODB-Dev] profiling zLOG and inspect

[Guido van Rossum]

> > > There's also the runtime cost of making calls to zLOG that won't do
> > > anything. I'd (lambda x: pass) all those calls out (if not
> > > environ.has_key()).
> > 
> > If you submit a patch to do that, we might consider it.  But I expect
> > that during the creation of the patch you'll find how inelegant the
> > approach you are proposing is.
> 
> Maybe, but do you see an alternative optimization that comes more
> elegantly? I'm attacking all the different parts, and the zLOG import
> comes up high in relation to other bits.

I'm confused.  The topic of your post is startup cost; yet here you
are discussing runtime cost, while you claim that your application
runs fast enough.  So why bother?  I sincerely doubt that the zLOG
calls cost much time.  Have you profiled it?

--Guido van Rossum (home page: http://www.python.org/~guido/)