6638ea9ca3
... and we have not that bad mapping type after all - lookup time is ~ the same as in one-attr instance. My namedtuple implementation on the other hand degrades awfully. So, need to rework it. First observation is that named tuple fields are accessed as attributes, so all names are interned at the program start. Then, really should store field array as qstr[], and do quick 32/64 bit scan thru it.
13 lines
210 B
Python
13 lines
210 B
Python
import bench
|
|
from _collections import namedtuple
|
|
|
|
T = namedtuple("Tup", "foo1 foo2 foo3 foo4 num")
|
|
|
|
def test(num):
|
|
t = T(0, 0, 0, 0, 20000000)
|
|
i = 0
|
|
while i < t.num:
|
|
i += 1
|
|
|
|
bench.run(test)
|