ZihanLi58 opened a new pull request, #3902: URL: https://github.com/apache/gobblin/pull/3902
Dear Gobblin maintainers, Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! ### JIRA - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR" - https://issues.apache.org/jira/browse/GOBBLIN-2024 ### Description - [ ] Here are some details about my PR, including screenshots (if applicable): We are seeing slowness in the GobblinMCEWriter, which will cause us huge backlog when handling large topic and affect the other topics in the same container for GMIP. After benchmark, we identify that we can improve the computeSpec part to reduce the duplicate work, also we can add the file size information in GMCE to avoid calling HDFS for each file. With this change, I verified that we can now process more than 7000 messages/minute vs 1000 messages/minute before the change. ### Tests - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: tested by running both ingestion and metadata pipelines, and verify to adopt this change, we need to apply change to metadata pipeline first. ### Commits - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 2. Subject is limited to 50 characters 3. Subject does not end with a period 4. Subject uses the imperative mood ("add", not "adding") 5. Body wraps at 72 characters 6. Body explains "what" and "why", not "how" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
