Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Mark Lawrence Newsgroups: comp.lang.python Subject: Re: Pyhon 2.x or 3.x, which is faster? Date: Tue, 8 Mar 2016 20:44:17 +0000 Lines: 58 Message-ID: References: <87d1r6iltx.fsf@elektro.pacujo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de e7kD9em2kPPG62aL+WCilwSBARMwkO174Ad6jobtbopQ== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'from:addr:yahoo.co.uk': 0.05; 'startup': 0.05; 'test,': 0.05; 'pypy': 0.07; 'start-up': 0.07; '0.1': 0.09; 'imported': 0.09; 'imports': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:which': 0.09; 'python': 0.10; 'assume': 0.11; 'properly': 0.15; '0.2': 0.16; 'defs': 0.16; 'disk.': 0.16; 'input.': 0.16; 'invoking': 0.16; 'modules,': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'seconds,': 0.16; 'seconds.': 0.16; 'timed': 0.16; 'worst': 0.16; 'wrote:': 0.16; 'module,': 0.18; 'tests': 0.18; 'input': 0.18; 'language': 0.19; '>>>': 0.20; 'lawrence': 0.22; 'file.': 0.22; 'code.': 0.23; 'header:In-Reply- To:1': 0.24; "i've": 0.25; 'header:User-Agent:1': 0.26; 'header:X -Complaints-To:1': 0.26; 'followed': 0.27; 'switch': 0.27; 'disk': 0.27; 'executing': 0.27; 'testing.': 0.29; 'starts': 0.29; 'that.': 0.30; 'compared': 0.30; 'seconds': 0.31; 'language.': 0.32; 'surely': 0.33; 'file': 0.34; 'but': 0.36; 'to:addr:python- list': 0.36; 'subject:?': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'one,': 0.37; 'doing': 0.38; "won't": 0.38; 'mean': 0.38; 'enough': 0.39; 'takes': 0.39; 'well.': 0.40; 'to:addr:python.org': 0.40; 'mark': 0.40; 'hang': 0.60; 'your': 0.60; 'charset:windows-1252': 0.62; 'matter': 0.63; 'our': 0.64; 'between': 0.65; '10000': 0.66; '>>>>>': 0.66; 'virtually': 0.66; 'here': 0.66; 'jobs': 0.67; '180': 0.84; 'hardly': 0.84; 'kicking': 0.84; 'nonsense.': 0.84; 'pythonistas,': 0.84; 'routines': 0.84; 'factors': 0.97 X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: 80.234.129.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:104358 On 08/03/2016 19:15, BartC wrote: > On 08/03/2016 16:09, Mark Lawrence wrote: >> On 08/03/2016 11:09, BartC wrote: >>> On 08/03/2016 02:45, Mark Lawrence wrote: >>>> On 08/03/2016 01:47, BartC wrote: >>> >>>>> The Python timing for that file is around 20 seconds, time enough to >>>>> read 10000 copies from the disk. >>>>> >>>>> And a C program reads /and decodes/ the same file from the same >>>>> disk in >>>>> between 0.1 and 0.2 seconds. >>>>> >>>> >>>> So how much of that time is Python startup time, compared to C which is >>>> effectively zero? >>> >>> Virtually zero as well. >> >> Nonsense. >> >>> >>> That's if by start-up time you mean how long between invoking Python >>> with the name of the main module, executing all the imports and defs in >>> the main and imported modules, until it starts properly executing code. >>> >>> In the jpeg test, perhaps 50ms. And it would not depend on the size of >>> the input since the start-up routines won't know that. >> >> How did you obtain that figure? > > By printing a message followed by exit(0) just before the program was > about to start doing its thing. > > Then I timed that using: > > $time python program.py > > in Linux. > > But this was hardly necessary as it was so obvious: it takes 150ms to > process a 300-pixel image, 20 seconds for a 2Mpixel one, and (I have to > switch to PyPy here as I've never had time to hang about for it) 180 > seconds for 80Mpixel file. > > Surely the start-up time would be the same no matter what the input. > Unless all of the background jobs are kicking in when you're testing. I assume that you do take such factors into account, by repeating your tests and taking an average, or perhaps even a worst case figure. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence