On Mon, Aug 10, 2009 at 3:19 PM, Branko Čibej<brane_at_xbc.nu> wrote:
> Mark Phippard wrote:
>> I have spent time on this and got it working. The performance speedup
>> was pretty minimal though. Windows does not come with a RAM disk
>> driver so you have to get something third party. Maybe they are not
>> high quality?
>> I am on Vista which makes this a little easier to setup because it has
>> a "mklink" command that lets you create a symbolic link, just as you
>> can on Unix. I setup a RAM disk and formatted it as NTFS. This is
>> important because FAT32 has a two-second timestamp resolution on files
>> and the test suite will slow itself down to accommodate that.
>> I then create a "tests" folder on the RAM disk and use the mklink
>> command to make a symbolic link from svn-tests-work to this folder. I
>> also pointed TEMP and TMP to the RAM disk.
>> It definitely works, but the speedup was just a couple minutes over
>> the entire test run.
> Hm, that's improbable. When I was still running the Windows tests, on a
> ramdisk, I got a very substantial speedup. I did have to put the whole
> tree on ramdisk, though, including source and binaries. Which makes for
> a fairly large ramdisk, and you have to enable test cleanup; several
> gigs of RAM does help here.
I did it similar to what the Unix users are doing. The repositories
and working copies are on RAM (and I enable test cleanup).
I tweeted my results at the time:
# Using RamDisk shaved 11 minutes off SVN 1.6.2 file:// tests. From
45 to 34 minutes. Running svn:// now
# Shaved 6 more minutes off the time to run the SVN tests by excluding
RAM drive from AV checking. Down to 28 minutes to run the tests.
So I did get a good speedup. I think I was comparing the total time
to what I am able to get on Unix or OSX which was still less (under 20
Keep in mind this was with 1.6.x. trunk cannot get anywhere close to
those times currently.
Received on 2009-08-10 21:27:45 CEST