In general not a good idea.
There are two numbers which have impact to scmactivity plugin performance.
1.) number of changesets
2.) number of files to blame
During the first running, scmactivity plugin has to collect all changesets and also blame all files. This could be optimised as I suggest in
For the next run, there are two possibilities.
A.) using only blame phase, this means that plugin has to blame all files for every run of plugin.
Disadvantage : if project has a lot of files, it can be really time consuming operation.
B.) compute files to blame from changesets and blame only changed file. This is today solution.
Disadvantage of this solutions depends on complexicity of computing changelog. This is cheap for changeset based VCS like Mercurial/GIT, but really expensive for file based VCS like CVS.
I suggest give user possibility to choose the way how to compute list of files to blame.
Maybe You can expand of my idea from
Name ot that option can be "use-changelog" with possible values :
- never .... never use changelog, always use blame for all files ( recommended for CVS )
- always... always use changelog, compute blame only for files in changelog ( recomended for small project and VCS with cheap changelog computation )
- not-for-first-run ... for first run don't use changelog, and after initialization use changelog ( recomended for project with many changesets )
If you look at my last patch
SONARPLUGINS-1561, there is not a lot todo with this idea.
I could implement this improvement, if you want.