RetroSearch Browse

Fri Jul 29 23:12:20 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-July/054997.html

Martin v. Löwis wrote:
> 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.

Was this with the file-system back end?  What is your current system?

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-July/054997.html below:

[Python-Dev] PEP: Migrating the Python CVS to Subversion