It shows a consistent 1-2% performance improvement.

Mean +- std dev: [property_base] 40.6 ns +- 0.6 ns -> [property_vectorcall] 40.0 ns +- 0.7 ns: 1.01x faster

Oops sorry, it was the wrong benchmark, it will be faster.. ;)

Mean +- std dev: [property_base] 140 ns +- 5 ns -> [property_vectorcall] 125 ns +- 2 ns: 1.12x faster

I updated the benchmark, and it shows 1.12x faster

New changeset 635bfe8162981332b36cc556bac78e869af579c2 by Dong-hee Na in branch 'main':
bpo-44661: Update property_descr_set to use vectorcall if possible. (GH-27206)
https://github.com/python/cpython/commit/635bfe8162981332b36cc556bac78e869af579c2

class Person:
    def __init__(self):
        self.__age = 0

    @property
    def age(self):
        return self.__age

    @age.setter
    def age(self, value):
        self.__age = value

p = Person()
p.age = 10 # Now become faster

> Mean +- std dev: [property_base] 140 ns +- 5 ns -> [property_vectorcall] 125 ns +- 2 ns: 1.12x faster

Ah! That's better. If it was only 1.01x faster, I would say that it's not worth it. But 1.12x is worth it. Thanks for this optimization.