A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2003-February/033661.html below:

[Spambayes] Re: [Python-Dev] Re: some preliminary timings

[Spambayes] Re: [Python-Dev] Re: some preliminary timings [Spambayes] Re: [Python-Dev] Re: some preliminary timingsT. Alexander Popiel popiel@wolfskeep.com
Tue, 25 Feb 2003 14:10:42 -0800
In message:  <15963.57541.244513.169979@montanaro.dyndns.org>
             Skip Montanaro <skip@pobox.com> writes:
>
>It's probably somewhat invalid to equate number of system calls with
>application runtime.  I redumped my last ktrace file just now with
>timestamps.  Here are some computed intervals:
>
>    interval                                    time
>    --------                                    ----
>    start -> open hammiefilter.pyc              0.071
>    open hammiefilter.pyc -> open hammie.db     0.516
>    open hammie.db -> close hammie.db           0.084
>    close hammie.db -> program end              0.011

This is good info.  Can you add in the time intervals between
loading each of the modules?  That might point out which modules
are actually expensive (or if it's none in particular).

- Alex



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4