coverlet
coverlet copied to clipboard
Performance improvement plan
Coverlet performance can be improved in two main areas
- Instrumentation and hits accounting/report generator phases
- Performance during test run related to "invasive" instrumentation
Possible plan:
- [ ] Create a BDN project with some tests for above main areas to have a baseline
Instrumentation and hits accounting/report generator phases
- [ ] Profile cpu/memory consumption to undestand where we spend time during instrumentation/hits report generation phases and optimize code
Performance during test run related to "invasive" instrumentation
- [ ] fold adjacents sequence point/branches instrumentation https://github.com/coverlet-coverage/coverlet/issues/307
- [ ] undestand if we suffer of false sharing due to in memory array storage and in case found a better structure
cc: @tonerdo @petli
I'd like to get started on benchmarking the instrumentation portion.. If no one else has already started on it.
We should add the exploration of P/Invoking of platform specific memory mapping APIs to the list
We should add the exploration of P/Invoking of platform specific memory mapping APIs to the list
There is an issue for it https://github.com/coverlet-coverage/coverlet/issues/808
This issue is stale because it has been open for 3 months with no activity.
This issue was closed because it has been inactive for 275 days since being marked as stale.