Python threading (was: Re: global interpreter lock not working as it should)
Michael Hudson
mwh at python.net
Wed Aug 7 07:15:46 EDT 2002
More information about the Python-list mailing list
Wed Aug 7 07:15:46 EDT 2002
- Previous message (by thread): Python threading (was: Re: global interpreter lock not working as it should)
- Next message (by thread): Python threading (was: Re: global interpreter lock not working as it should)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
a-steinhoff at web.de (Armin Steinhoff) writes: > As an intermediate solution I have only inserts two > lines in cevel.c ... here some performance numbers. > > Performance unmodified: > > time ../../python test_threading.py Are you aware what test_threading does? Lines like delay = random.random() * 2 make me doubtful of the use of this test as a benchmark... [...] > 4.16s real 0.14s user 0.02s system [...] > 2.66s real 0.16s user 0.02s system > # > > The performance is increased by ~90 % Even given the apparent uselessness of this benchmark, where do you get 90% from here? Cheers, M. -- if-you-need-your-own-xxx.py-you-know-where-to-shove-it<wink>-ly y'rs - tim -- Tim Peters dishes out versioning advice on python-dev
- Previous message (by thread): Python threading (was: Re: global interpreter lock not working as it should)
- Next message (by thread): Python threading (was: Re: global interpreter lock not working as it should)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list