search

mindflayer / python-mocket

a socket mock framework - for all kinds of socket animals, web-clients included
BSD 3-Clause "New" or "Revised" License
279 stars 41 forks source link

Improve efficiency on CI #194

Closed amotl closed 1 year ago

amotl commented 1 year ago

Dear Giorgio,

this is another improvement to the CI configuration, in order to optimize resource usage. I hope you like it.

With kind regards, Andreas.

sonarcloud[bot] commented 1 year ago

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

mindflayer commented 1 year ago

Awesome, thank you!

amotl commented 1 year ago

At [1], it now says "pip cache is not found", and at [2], you see that 13 MB worth of cache content have been saved. You may want to manually re-run the same workflow now, to see that the cache is properly re-used.

[1] https://github.com/mindflayer/python-mocket/actions/runs/3610529308/jobs/6084381221#step:3:15 [2] https://github.com/mindflayer/python-mocket/actions/runs/3610529308/jobs/6084381221#step:13:4

amotl commented 1 year ago

Resource usage

Cold cache: https://github.com/mindflayer/python-mocket/actions/runs/3610529308/usage Warm cache: https://github.com/mindflayer/python-mocket/actions/runs/3610554332/usage

Thoughts

Almost all jobs show speedups, but the PyPy job experiences a significant slowdown. I hope it's only a fluke. Let's monitor this.