Sandcastle December CTP takes a much longer time

When I updated from the November CTP to the December CTP, the "BuildAssembler" step of my build went from 2 minutes to 50 minutes.

I'm running this in a virtual machine without a ton of resources, and I haven't seen any other posts about this, so I'm wondering if the December CTP is handling resources differently such that my particular configuration comes out on the losing end.

[396 byte] By [RobCavicchio] at [2007-12-27]
# 1

It could be that it's having trouble connecting to the MSDN web service to resolve links to online content. If you're using the help file builder, set the SdkLinkType property to None to disable it. If you're using some other build script, edit your sandcastle.config file and modify the line in the ResolveReferenceLinksComponent to set the link type to None:

<targets files="C:\Program Files\Sandcastle\Data\Cpref_reflection\*.xml" type="None">

If the build time returns to normal after that, it was probably the cause. Sometimes the web service is slower than at other times but I haven't seen it that slow.

Eric

EWoodruff at 2007-9-3 > top of Msdn Tech,Visual Studio,Developer Documentation and Help System...
# 2
Thanks for the suggestion Eric, but that doesn't solve the problem.
RobCavicchio at 2007-9-3 > top of Msdn Tech,Visual Studio,Developer Documentation and Help System...
# 3
Hello Rob,

I encountered the same problem; after upgrading Sandcastle to the December CTP, our nightly server build is taking much more time to generate the documentation. Build duration suddenly increased from around 10 minutes to more than 2 hours!

Then I noticed that the BuildAssembler step currently uses upto 500Mb of memory. My local developer machine has 1Gb RAM, so the whole process could be executed in-memory in under a minute. However, our build server only has a meager 256 Mb RAM...

So apparently Sandcastle (or more specifically, the BuildAssembler) consumes a considerable amount of memory, and slows down tremendously if not enough physical memory is present on the target machine.

Hope this helps!
Zef at 2007-9-3 > top of Msdn Tech,Visual Studio,Developer Documentation and Help System...
# 4
Yes, thank you, that explains it. I suspected something like that might be going on, but it's good to have confirmation. I'll have to see if I can find a better machine to run it on.
RobCavicchio at 2007-9-3 > top of Msdn Tech,Visual Studio,Developer Documentation and Help System...

Visual Studio

Site Classified