reflection: Use fast ZPP for ReflectionProperty::(get|set)Value() #16329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the Doctrine Core Team Meetup 2024 the Doctrine team investigated the performance overhead of using
setRawValueWithoutLazyInitialization()
instead ofsetValue()
and came to the surprising conclusion thatsetRawValueWithoutLazyInitialization()
outperformedsetValue()
, despite doing more work.These two scripts are used as the benchmark:
and
Benchmarking these with a current git master shows that
setValue()
is 50% slower:Looking into the “why” revealed that the
setValue()
script spent quite some time inzend_parse_parameters()
.A 50% overhead can be significant, given that
setValue()
is commonly called several thousand times in a single request when using Doctrine.This commit changes the non-static property case of
setValue()
to make use of the fast parameter parsing API and adjustsgetValue()
for consistency.The resulting comparison shows that both
setValue()
andsetRawValueWithoutLazyInitialization()
are now (almost) equal: