I'm gonna bump this in the hope of getting some kind of official response, as this issue is a constant, if relatively mild, annoyance.
Hi there, Can you try SmartSVN 7.6 and let us know if you still have problems please? We made a number of performance improvements with this release, so hopefully you'll see a difference.
I'm running 7.6 and I get bombarded with this message too. In my case I don't notice much difference before or after I run the "clean up". Merges and branch swiching in SVN is glacial "by design" so if the degradation factor only 2-3x I probably wouldn't notice. I'd prefer it if SmartSVN would run a clean up automatically when I switch branches and similar (something I do many times a day), or just shut up about it.
Hello aheid, We have SmartSVN 8 now and again there have been some performance improvements so I'd recommend giving that a go. Of course, if you're still seeing this on 8 I can look into requesting a future improvement that might prevent the repeated messages - I understand how annoying that might be for you and indeed other users.
Thanks for the follow up Liam. I'm planning to install version 8 this week, I'll post some feedback on that. It would be nice to know what sort of performance degradation the message warns about though. Is it general for all operations or are some operations (merging or annotating fex) affected more than others?
Thank you aheid, I do strongly recommend using 8 now and look forward to any feedback you have on it. The performance degradation will be related to client side operations, specifically refreshing. The clean up should stop the message popping up.
So been running version 8 for a couple of weeks now, and I did get the message twice (once was mere minutes after I did a clean-up due to aborted branch switch). However that's just twice, which is considerably less than I used to get. So I'm pleased so far. Though I would still like an option to make SmartSVN auto-cleanup when switching branches or updating, if it deems it necessary.
Hi aheid, good to hear back from you. Thanks for the feedback, I'm glad you're pleased so far. There should be further performance improvements in the next few releases too. With regard to the possibility of an auto-cleanup in SmartSVN (it's actually a Subversion issue, not specific to SmartSVN), it's possible that there could be false positive detections and as it's a working copy modifying action it was decided best to be left for the user to decide whether or not to run cleanup.
Hi aheid, We think that in this case the message is shown because the timestamps for a considerable amount of the files at least do not match the timestamps in the SVN metadata. The message essentially means (usually), that the file stamps were different (indicating change), but the actual file content is the same (no change). This results in a performance problem, since each status has to compare all of the file content instead of just comparing dates. I suspect that with the performance improvements expected in the 8.5 release candidate you will see a further reduction in these performance issues.
Thanks for the feedback Liam, I'm not sure how the timestamps could change in this situation, but at least it's something I can look into (if for nothing else to settle my own curiosity). Perhaps the IDE components are to blame. In any case, I'll be looking forward to the 8.5RC. Thanks again.