S3 Ingest Performance #23090
Unanswered
satellite-no
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have large (16 cpu) AWS instances ingesting data from s3 using the sqs polling. The nodes dont seem to be doing much at around 20% CPU but I still get a backlog of SQS messages when I reduce the number of nodes polling. Currenty im using default settings for sqs. But I've tried different combinations of poll_sec, client_concurrancy, and max_number_of_messages. But total ingest seems to stick at around 50MB/s.
Any thoughts?
File sizes in s3 range a lot but are generally around 20MB.
s3 Config:
Beta Was this translation helpful? Give feedback.
All reactions