[
https://issues.apache.org/jira/browse/CAMEL-14514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133267#comment-17133267
]
Øystein William Grændsen commented on CAMEL-14514:
--------------------------------------------------
[[email protected]] :
I'm all for making things faster and more effective, but the removal of
AckDeadline actually disables the option to do retry backoff from camel without
introducing external tools. We have been using this component for a couple of
years now and this breaking change stops us atm. of upgrading from 3.1.0 and
on. Is there any reason why this option has been removed when it's still
available in google ?
> Improving Google Pub/Sub performance
> ------------------------------------
>
> Key: CAMEL-14514
> URL: https://issues.apache.org/jira/browse/CAMEL-14514
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-pubsub
> Affects Versions: 3.1.0
> Reporter: Alvin Kwekel
> Priority: Major
> Labels: performance
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I want to explore if it's possible to improve the performance of the Google
> Pub/Sub component.
> I did some experimenting with replacing the
> com.google.apis:google-api-services-pubsub library with
> com.google.cloud:google-cloud-pubsub and replacing the synchronous pull with
> the asynchronous one. I've also created a cache for the message producers.
> This combination lead to a significant improvement. More than 50 times faster
> in a simple test with a producer in a splitter with parallel processing and a
> consumer with concurrent consumers.
> I'd like to invite the community to see if these changes are in right
> direction and help out to take it further.
> PR: [https://github.com/apache/camel/pull/3551]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
