Re: Module load times

References	<mqiq69$n8p$1@ger.gmane.org> <mailman.177.1439500385.3627.python-list@python.org> <55cd4e0c$0$1642$c3e8da3$5496439d@news.astraweb.com> <a3f1023b4c03456b9ba1cdeafdd29f8d@exch.activenetwerx.com>
Date	2015-08-14 12:38 +1000
Subject	Re: Module load times
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.1.1439519917.4764.python-list@python.org> (permalink)

Show all headers | View raw

On Fri, Aug 14, 2015 at 12:25 PM, Joseph L. Casale
<jcasale@activenetwerx.com> wrote:
> Yeah that wasn't clear. The plugins are invoked in fresh interpreter processes
> and hence modules with import side effects or simply large modules can
> manifest over time.

If they're invoked in fresh processes, then you're looking at process
startup time, and I would recommend using OS-level tools to play
around with that. Unix-like systems will usually have a 'time' command
which will tell you exactly how much wall and CPU time a process took
needed; just create a system that starts up and promptly shuts down,
and then you can test iterations that way.

Of course, there are a million and one variables (disk caches, other
activity on the system, etc), but it's better than nothing.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Module load times "Joseph L. Casale" <jcasale@activenetwerx.com> - 2015-08-13 21:12 +0000
  Re: Module load times Steven D'Aprano <steve@pearwood.info> - 2015-08-14 12:10 +1000
    RE: Module load times "Joseph L. Casale" <jcasale@activenetwerx.com> - 2015-08-14 02:25 +0000
    Re: Module load times Chris Angelico <rosuav@gmail.com> - 2015-08-14 12:38 +1000

csiph-web