Skip to content

feat(#1798) Performance fix for topic send#1792

Open
jeanouii wants to merge 2 commits intoapache:mainfrom
jeanouii:fix/topic-send-per-destination-locking
Open

feat(#1798) Performance fix for topic send#1792
jeanouii wants to merge 2 commits intoapache:mainfrom
jeanouii:fix/topic-send-per-destination-locking

Conversation

@jeanouii
Copy link
Copy Markdown
Contributor

To be discussed

@jeanouii jeanouii changed the title [#TODO] Performance fix for topic send feat(#1798) Performance fix for topic send Mar 18, 2026
@jeanouii jeanouii force-pushed the fix/topic-send-per-destination-locking branch from 8cf513f to be653cb Compare March 25, 2026 23:31
@cshannon
Copy link
Copy Markdown
Contributor

@jeanouii - This is an interesting find, I didn't even notice that synchronized keyword on that method. Most of the synchronization happens internally on the various collections etc. and I looked and I didn't see synchronized use anywhere else on the topic object itself internally.

Did you look around the broker to see if anything happens to synchronize the topic externally? The destinations often get referred to more generic as RegionDestination plus there's various wrappers so saerching might be tricky. I will search too, I just am curious if anything else is synchronizing on the Topic's intrinsic lock that would now break if we switch the lock.

I guess there's always the risk of breaking existing plugins (if they were synchronizing for some reason on the topic) but we can't control any custom code so not much we could do in that scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants