Jim Fulton wrote: > I don't expect that this would be an issue for Python. Right. > 2. I initially tried to conver our entire repository, including all > branches. This would have taken days. I finally decided to just > convert our trunk, which took several hours. The main time > sink was in the load step of the conversion process. > > I suspect that much of the time hit was due to the Berkely DB > back end. I think I've heard that the file-system-based back end > is much faster in general. Dunno. For the Python CVS (which translates into some 40,000 revisions), on the machine which I was originally using (1GHz Pentium), conversion took 7h. On my current workstation, it takes a little over an hour. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4