gh-100176: Remove outdated Tools/{io,cc,string}bench

[hugovk]

Closes#32135.
Closes#100176.
Closes#100197.

See:

• Meta issue: clean up redundant compat code #100176 (comment)
• https://discuss.python.org/t/do-we-still-need-tools-io-cc-string-bench/22557

Replaces and:

• closesbpo-n/a: Updated ccbench.py used to assess multithreading #32135.
• closesgh-100176: Tools/iobench: Remove redundant compat code for Python <= 3.2 #100197.

• Issue: Meta issue: clean up redundant compat code #100176

[arhadthedev]

BTW, it allows to close gh-32135 as outdated.

[sobolevn]

@rhettinger had some opinion on this as well.

[erlend-aasland]

Sad to see Håvamål go 😢👁️

cpython/Tools/iobench/iobench.py

Lines 482 to 548 in 81e3aa8

	1.
	Gáttir allar,
	áðr gangi fram,
	um skoðask skyli,
	um skyggnast skyli,
	því at óvíst er at vita,
	hvar óvinir
	sitja á fleti fyrir.
	2.
	Gefendr heilir!
	Gestr er inn kominn,
	hvar skal sitja sjá?
	Mjök er bráðr,
	sá er á bröndum skal
	síns of freista frama.
	3.
	Elds er þörf,
	þeims inn er kominn
	ok á kné kalinn;
	matar ok váða
	er manni þörf,
	þeim er hefr um fjall farit.
	4.
	Vatns er þörf,
	þeim er til verðar kemr,
	þerru ok þjóðlaðar,
	góðs of æðis,
	ef sér geta mætti,
	orðs ok endrþögu.
	5.
	Vits er þörf,
	þeim er víða ratar;
	dælt er heima hvat;
	at augabragði verðr,
	sá er ekki kann
	ok með snotrum sitr.
	6.
	At hyggjandi sinni
	skyli-t maðr hræsinn vera,
	heldr gætinn at geði;
	þá er horskr ok þögull
	kemr heimisgarða til,
	sjaldan verðr víti vörum,
	því at óbrigðra vin
	fær maðr aldregi
	en mannvit mikit.
	7.
	Inn vari gestr,
	er til verðar kemr,
	þunnu hljóði þegir,
	eyrum hlýðir,
	en augum skoðar;
	svá nýsisk fróðra hverr fyrir.
	8.
	Hinn er sæll,
	er sér of getr
	lof ok líknstafi;
	ódælla er við þat,
	er maðr eiga skal
	annars brjóstum í.

[hugovk]

(Resolved conflict)

[Sophist-UK]

I would have commented sooner had I known that this was about to happen. It would have been helpful if someone had commented in my PR to ccbench.py that this was being considered so that I would have been notified and might have had a chance to comment before it happened.

I believe it was clear from the extensive discussion about the shortcomings of the current GIL in faster-cpython that the ccbench script is still useful - because it clearly identifies an ongoing performance issue when multithreading with one or more CPU-heavy threads.

That said, I do understand that performance scripts do not really have a place in the cpython source code repo, but unfortunately I do not have the time to rework the updated ccbench script for the pyperformance suite, so I guess it is going to just disappear.

[hugovk]

I would have commented sooner had I known that this was about to happen. It would have been helpful if someone had commented in my PR to ccbench.py that this was being considered so that I would have been notified and might have had a chance to comment before it happened.

Apologies, I'll ping next time this sort of thing comes up. (btw we wouldn't be allowed to merge your PR because it looks like the CLA isn't signed.)

That said, I do understand that performance scripts do not really have a place in the cpython source code repo, but unfortunately I do not have the time to rework the updated ccbench script for the pyperformance suite, so I guess it is going to just disappear.

Yep, in general, benchmarks are much more useful in pyperformace, because they're run often and people pay attention to their results.

The code hasn't disappeared, it's still in the 3.12 and older branches, and in Git history.

And of course, if there's consensus we can easily revert/re-add bits of this.

[Sophist-UK]

btw we wouldn't be allowed to merge your PR because it looks like the CLA isn't signed.

Go look at the PR history - I signed the CLA and the relevant label was added. Later the label was removed for some reason unknown to me..