2009/3/24 Daniel Stutzbach <dan...@stutzbachenterprises.com>: > On Tue, Mar 24, 2009 at 10:13 AM, Mark Dickinson <dicki...@gmail.com> wrote: >> >> 2009/3/24 Daniel Stutzbach <dan...@stutzbachenterprises.com>: >> > [...] >> > 100 nanoseconds, py3k trunk: >> > ceval -> PyObject_GetItem (object.c) -> list_subscript (listobject.c) -> >> > PyNumber_AsSsize_t (object.c) -> PyLong_AsSsize_t (longobject.c) >> > [more timings snipped] >> >> Does removing the PyLong_Check call in PyLong_AsSsize_t >> make any noticeable difference to these timings? > > Making no other changes from the trunk, removing the PyLong_Check and NULL > check from PyLong_AsSsize_t shaves off 4 nanoseconds (or around 4% since the > trunk is around 100 nanoseconds). > > Here's what I'm testing with, by the way: > > ./python.exe Lib/timeit.py -r 10 -s 'x = list(range(10))' 'x[5]'
What difference does it make on real applications? Are you running any macro-benchmarks against this? Collin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
