Consider reverting optimization in normalization #540

Activity

1. jaraco commented on Jul 14, 2026

   

   jaraco

   on Jul 14, 2026

   MemberAuthor

   More actions

   As a baseline, here are a couple of snapshots of the performance tests without any diff:

   exercises.py:cached distribution: 128 µsec (-2 µsec, -2%)
   exercises.py:discovery: 129 µsec (-1 µsec, -1%)
   exercises.py:entry_points(): 1.47 msec (+40 µsec, 3%)
   exercises.py:entrypoint_regexp_perf: 48.7 µsec (0 nsec, 0%)
   exercises.py:normalize_perf: 93.3 nsec (+2.1 nsec, 2%)
   exercises.py:uncached distribution: 215 µsec (-5 µsec, -2%)
   

   exercises.py:cached distribution: 131 µsec (0 nsec, 0%)
   exercises.py:discovery: 132 µsec (-2 µsec, -1%)
   exercises.py:entry_points(): 1.45 msec (-10 µsec, -1%)
   exercises.py:entrypoint_regexp_perf: 49.5 µsec (+200 nsec, 0%)
   exercises.py:normalize_perf: 87.8 nsec (-1.3 nsec, -1%)
   exercises.py:uncached distribution: 220 µsec (+1 µsec, 0%)
   

   I've seen even higher numbers in the 3-4% range.

   So there's quite a bit of jitter in the tests, meaning we'd probably want to see 6% or better improvement to justify a change.
2. jaraco

   added 2 commits that reference this issue on Jul 14, 2026

   Revert normalize performance changes (gh-143658) in __init__.py

   ...

   This issue will close once commit 89e9eb7 is merged into the 'main' branch.

   89e9eb7

   Revert normalize performance changes (gh-143658) in __init__.py

   ...

   This issue will close once commit 73efee2 is merged into the 'main' branch.

   73efee2