[pack] Increasing the perf of extensions
Issue describing the changes in this PR
resolves #issue_for_this_pr
Pull request checklist
- [x] My changes do not require documentation changes
- [ ] Otherwise: Documentation issue linked to PR
- [ ] My changes should not be added to the release notes for the next release
- [ ] Otherwise: I've added my notes to
release_notes.md
- [ ] Otherwise: I've added my notes to
- [x] My changes do not need to be backported to a previous version
- [ ] Otherwise: Backport tracked by issue/PR #issue_or_pr
- [ ] My changes do not require diagnostic events changes
- Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
- [ ] I have added all required tests (Unit tests, E2E tests)
Additional information
Additional PR information
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
@shrohilla I realize this is still in draft, but the title made me curious :)
To better describe the changes here, it would be good to remove Kafka from the description as this is not Kafka specific.
Have you done any measurements here?
@shrohilla I realize this is still in draft, but the title made me curious :)
To better describe the changes here, it would be good to remove Kafka from the description as this is not Kafka specific.
Have you done any measurements here?
@fabiocav for Kafka out of proc apps it worked well, while no change for perf for eventhub, but I only tested for kafka and Eventhub that too for python app.
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
No longer required synced offline with @mathewc and found the solution in kafka extension