Proposal:

Back in 2013, it was determined that caching the result oftuple_hash did not have any significant speedup.

However, a lot has changed since then, and in arecent experiment to add a tuple hash cache back in, themdp benchmark increased by 86%.

Admittedly, there was no measurable improvement on any other benchmark, but it also seems to have no downside, including formemory usage when measured withmax_rss.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

• [ ]

Linked PRs

• gh-131525: Cache the result of tuple_hash #131529
• gh-131525: Remove_HashedSeq wrapper fromlru_cache #131922