| Summary: | Subversive Revert Operation Painfully Slow | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Steve Cohen <scohen> |
| Component: | Core | Assignee: | Igor Burilo <igor.burilo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bernd.vogt, dbharris, jtk499 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 287559 | ||
|
Description
Steve Cohen
I've experienced this as well. A cursory examination of SVNKit source implies that the problem might be there - there are a large number of sleepForTimestamp() calls that seem to wait for the system clock to tick over enough for a filesystem timestamp to be updated. A Thread.wait() ensues. However, that method does appear to allow these sleep calls to be overridden. Perhaps Subversive can specify this? I have checked through the code, there is no code in Subversive that could cause any delays. And SVNKit 1.3.5 does not contain any kind of "delays" or "sleeps" either. Moreover, Subversive performs caching of the SVN connector library instances in order to improve overall performance. So, may be somewhere in the SVN client libraries a non-optimal implementation code for the revert operation exists, but unfortunately there is nothing that could be done on our side in order to improve revert performance. For what it's worth, I no longer notice this problem. Probably should have specified the version in the original bug report, but from its date, I'm sure I have upgraded this plugin since then. (In reply to comment #3) Thank you for your information. It is really good to be sure that the newer SVN Kit version does not cause the problem anymore. I've found the case when the problem reappears even with the latest SVN Kit connector. It is the case when you perform revert from the Synchronize View. Since in this case it is working on per-resource basis in order to not touch any unnecessary resources, part of SVN Kit implementation causes the issue. I've disabled corresponding part of the SVN Kit code. |