Faster "Pending changes" updates

[David Cañadas 0]

Hello,

We've started to experience long times waiting the "Pending changes" tab to update. Even disabling the auto-refresh feature, it tooks from 15 to 30 seconds to update, no matter how many changes we have. Other options such checking timestamps then hashes, or modifying the move detection settings didn't improve the update time.

I was wondering whether there is a way to accelerate such updates in some manner, or if you have any kind of file watcher service that looks for changes in real-time instead of inspecting in "Pending changes" update-time that we can use.

Best.

[calbzam 97]

Hi JDavid,

If you open the "Pending Changes" view --> Options, you will probably have enabled the options marked with * . These operations a require disk search (locally move detection...). With big workspaces it could take a while. If this is your case reconfigure the options according to your needs.

Anyway, if you attach the Plastic client log, we can review where the pending changes calculation is spent.

Regards,
Carlos

[David Cañadas 0]

I am so sorry but I don't understand what you mean with "options marked with *". In my Pending changes/Options window there are no options marked with *.

[calbzam 97]

Sorry, I think this text was removed in a recent Plastic client version. If you disable the move detection, the pending changes calcualtion should be faster. 

Anyway, let's review the Plastic client logs to understand where the time is spent refreshing this view.

Regards,

Carlos.

[David Cañadas 0]

Edited

The problem is happening to more than one user. They followed the instructions here with no noticeable improvement: http://blog.plasticscm.com/2018/05/debugging-pending-changes-view-performance.html

The logs for the particular user that raised the request:

2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher - -------ProcessChanges:--------
2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -     timerGetMountPoint 30 ms, 223988 times
2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -     timerProcessChange 62 ms, 223988 times
2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -         timerIsBinaryPath 0 ms, 0 times
2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -             timerIsBinaryTypePredictor 0 ms, 0 times
2020-11-27 10:58:12,228 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -     timerGetChangeTypes 295 ms, 223988 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -         timerGetIgnoredTypes 16 ms, 2926 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -         timerGetCloakedTypes 32 ms, 223988 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -         timerCheckChanged 63 ms, 196851 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -         timerGetHiddenTypes 0 ms, 15 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -     timerNeedToProcessChildren 47 ms, 223988 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher -     timerGetFsNodes 14284 ms, 24211 times
2020-11-27 10:58:12,229 <OMITTED> DEBUG WorkspaceStatus: DiskChangesSearcher - Get changes total time: 15078

Our disk drives are:

WD Black SN750 NVMe 2 SSD WDS (where system and Plastic SCM software resides); and

Adata XPG GAMMIX S11 Pro (where we locate our workspaces).

[calbzam 97]

Hi,

Do you have "ingnore.conf/hidden_changes.conf" in this workspace?

Could you check if temporary removing them, the pending changes calculation is fater?

Regards,

Carlos.

[David Cañadas 0]

Here you have it.

Yes, calculations speeded up without hidden/ignored files/patterns; from 15-30 to about 5-7 seconds.

Please find the corresponding logs attached.

 

plastic.debug.log.20201210.txt plastic.relevant.log.20201210.txt

[calbzam 97]

Ok, so the key seems to be your ignore/hidden_changes rules. Could you attach these configuration files?

Regards,

Carlos.

[David Cañadas 0]

Sure. Some stuff renamed just for confidentiality purposes.

hidden_changes.conf ignore.conf

[calbzam 97]

Hi David,

Could you reach us via private message? I want to check if it's possible to have access to this repo reproduce and debug the problem with your same ignore/hidden_changes rules.

Regards,

Carlos.

[David Cañadas 0]

Sent them a few days ago.

[calbzam 97]

Hi David,

We sent you the NDA to be signed. Do you need something more from our side?

Regards,

Carlos.