Github user arkadius commented on the issue:
https://github.com/apache/nifi/pull/3111
@markap14 No problem, looking forward for conclusions from this testing.
---
Github user arkadius commented on the issue:
https://github.com/apache/nifi/pull/3111
@markap14 I understand your point, I also don't like poems in comments :-)
I've switched to Caffeine in all places except 4. Can you look at this now? CI
report failure in some jobs - looks like non
Github user arkadius commented on the issue:
https://github.com/apache/nifi/pull/3111
Other places of usage:
1. `org.apache.nifi.record.path.util.RecordPathCache` - record path cache,
synchronized access
2. `org.apache.nifi.avro.AvroReader` - avro schema cache (this parts
Github user arkadius commented on the issue:
https://github.com/apache/nifi/pull/3111
@markap14 what do you think about using
https://github.com/ben-manes/caffeine instead? They have benchmarks showing
performance difference from current approach (named `LinkedHashMap_Lru`). Take
Github user arkadius commented on the issue:
https://github.com/apache/nifi/pull/3111
Hi @markap14 . Thank you for your reply. We have a quite heavy-loaded
environment. We are processing about 5 GB / min of messages on 32 core host.
Avro serialization was our main bottleneck. We had
GitHub user arkadius opened a pull request:
https://github.com/apache/nifi/pull/3111
AvroRecordSetWriter - Fix for slow synchronized access to
compiledAvroSchemaCache
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review
