René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Update lockbench.py","articleBody":"# Feature or enhancement\n\nThe lockbench.py benchmarks `PyMutex` and `PyThread_type_lock` for various number of threads and length of critical section. You'll see similar benchmarks for other mutex implementations: [Rust parking_lot](https://github.com/Amanieu/parking_lot/tree/master/benchmark/src/bin), [WebKit](https://github.com/WebKit/WebKit/blob/main/Source/WTF/benchmarks/LockSpeedTest.cpp).\n\nI'd like to make a few updates to this benchmark:\n\n* Remove `PyThread_type_lock`. It's now based on `PyMutex`, so this isn't really useful anymore.\n* Add `--work-outside` to adjust the amount work done while *not* holding the lock. This helps simulate low and moderate contention scenarios.\n* Add `--num-locks`. So if we run with 8 threads and 2 locks, each group of 4 threads is independently contending for a lock. This adds more concurrency and helps demonstrate the limits of excessive spinning.\n* Make number of threads configurable\n* Add `--total-iters` which configures each thread to run for a fixed number of iterations instead of the default of running the whole benchmark for 1 second. With this mode, the benchmarks is only as fast as the slowest thread. It's another way to measure the effect of \"fairness\".\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-145231\n* gh-145271\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/colesbury","@type":"Person","name":"colesbury"},"datePublished":"2026-02-25T18:56:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/145230/cpython/issues/145230"}