Codingaditya17 commented on PR #67519:
URL: https://github.com/apache/airflow/pull/67519#issuecomment-4548259814

   Sure, I ran the provider footprint benchmark locally using the script from 
the gist linked in #67515.
   
   Command used on both before and after:
   
   `uv run --project airflow-core python dev/analyze_provider_footprints.py -p 
elasticsearch --runs 5 --markdown`
   
   Before this PR, with the module-level Elasticsearch client import:
   
   | Provider | Time Delta | Memory Delta | Modules Loaded | Top 3rd-Party 
Packages |
   
|----------|-----------:|-------------:|---------------:|------------------------|
   | `elasticsearch` | 254ms (+23%) | +58.8MB (+64%) | 685 (1 tested) | 
`requests`, `elasticsearch`, `numpy`, `chardet` (+18) |
   
   After this PR, with the Elasticsearch client import lazy-loaded:
   
   | Provider | Time Delta | Memory Delta | Modules Loaded | Top 3rd-Party 
Packages |
   
|----------|-----------:|-------------:|---------------:|------------------------|
   | `elasticsearch` | 19ms (+2%) | +2.3MB (+2%) | 53 (1 tested) | `sqlparse`, 
`wrapt`, `deprecated`, `more_itertools` |
   
   So on my machine, this reduced the provider import delta by about 235ms, 
reduced memory delta by about 56.5MB, and reduced provider-loaded modules by 
632.
   
   I restored the branch after benchmarking, so there are no benchmark/script 
changes included in the PR.


-- 
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]

Reply via email to