-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java subscriber throughput limited to 130,000 qps #4485
Labels
api: pubsub
Issues related to the Pub/Sub API.
type: question
Request for information or clarification. Not an issue.
Comments
ajaaym
added
type: question
Request for information or clarification. Not an issue.
api: pubsub
Issues related to the Pub/Sub API.
labels
Feb 12, 2019
@jadekler, @kolea2 FYI. Let's discuss this offline. Please include Kir in the conversation. |
👍 |
sure. dpcollins@. Put something on my calendar. |
This was referenced Feb 18, 2019
Closed
Closed
Closed
@dpcollins-google, can we close this? |
Yes, I thought it would be automatically closed by putting resolves in the
last pr description. You can close or I can when I get home.
…On Thu, Mar 14, 2019, 1:53 PM Solomon Duskis ***@***.***> wrote:
@dpcollins-google <https://github.com/dpcollins-google>, can we close
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4485 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Amn1sv9I-pcXrR307T1PHbNG7R1g5m0Lks5vWox-gaJpZM4a4MyK>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: pubsub
Issues related to the Pub/Sub API.
type: question
Request for information or clarification. Not an issue.
Environment details
Steps to reproduce
Code snippet
Any additional information below
I've been working to improve the Cloud Pub/Sub loadtest framework. I've been unable to achieve the same throughput in java as I have in golang under the same conditions. I'm unable to increase subscriber throughput on a 16 core machine beyond 130MB/s with 1KB messages, but have been seeing 300+MB/s rates with golang under the same conditions. I've also tried setting the channel provider and executors to different values to no avail. Since the cpu load is stuck at about 35%, perhaps this is a contention or artificial limitation somewhere else in the client library?
In progress branch for updates here https://github.com/dpcollins-google/pubsub/tree/loadtest_updates
The text was updated successfully, but these errors were encountered: