[
https://issues.apache.org/jira/browse/AVRO-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691044#comment-17691044
]
ASF subversion and git services commented on AVRO-3713:
-------------------------------------------------------
Commit ad5cf6857e28b655304a5f7f411c9d63f4ac3909 in avro's branch
refs/heads/dependabot/maven/lang/java/com.diffplug.spotless-spotless-maven-plugin-2.33.0
from Niels Basjes
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=ad5cf6857 ]
AVRO-3713: [Java] Fix Map synchronization regression
Signed-off-by: Niels Basjes <[email protected]>
> Regression AVRO-1760 : Thread scalability problem with the use of
> SynchronizedMap
> ---------------------------------------------------------------------------------
>
> Key: AVRO-3713
> URL: https://issues.apache.org/jira/browse/AVRO-3713
> Project: Apache Avro
> Issue Type: Bug
> Reporter: Niels Basjes
> Assignee: Niels Basjes
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> This is a regression of AVRO-1760 which is causing production performance
> problems.
> In AVRO-1760 the issue was fixed that there is a scalability problem with
> AVRO being used in multithreaded situations.
> The solution that was implemented for this ticket uses a different Map
> implementation (part of Guava) that does not have these locking issues:
> [https://github.com/apache/avro/commit/363360229e7ea5f816d87f9d5747dd4494d3b862#diff-422f44890f5e0ab1f508a7c75d0d18fc7831a1c3ca13e0c97780617570c50d5cL970-L973]
> Investigating the performance of our internal application has made us
> conclude the original problem was reintroduced with this commit:
> [https://github.com/apache/avro/commit/c78a3d5ea4e7e511ba9f6182157956db3e65e1a0#diff-422f44890f5e0ab1f508a7c75d0d18fc7831a1c3ca13e0c97780617570c50d5cL986-L988]
> which seems to be related to this jira AVRO-2265 "Remove Guava as a
> dependency".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
