Github user chermenin commented on the issue:
https://github.com/apache/flink/pull/3021
I've got results and here are:
Benchmark | Mode | Cnt | Score | Error | Units
-------------------|-------|------|-----------|---------|--------
Just operation | avgt | 200 | 74.672 | 0.944 | ns/op
if-else (_not_ null value) | avgt | 200 | 915.718 | 5.534 | ns/op
try-catch (_not_ null value) | avgt | 200 | 74.183 | 0.405 | ns/op
if-else (null value) | avgt | 200 | 901.775 | 5.368 | ns/op
try-catch (null value) | avgt | 200 | 8649.317 | 40.462 | ns/op
In this way `if-else-check` always adds more than 800 nanoseconds per
operation to run-time.
While `try-catch-block` doesn't slow down normal performance. We really
need this option, because null value isn't normal value for us now. I will
change the code in the closest future.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
