From: SourceForge.net <no...@so...> - 2005-04-14 15:15:05
|
Support Requests item #1155925, was opened at 2005-03-04 02:31 Message generated for change (Comment added) made by kdowns You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=416079&aid=1155925&group_id=36057 Category: None Group: None Status: Open Priority: 5 Submitted By: Brian (brisls1) Assigned to: Kevin Downs (kdowns) Summary: Slow Processing Speed Initial Comment: I have an automated build that is running nDoc on a Visual Studio solution. It takes over 12 minutes to finish generating the documentation. Any way to speed this up? Hardware suggestion? Configuration suggestions? TIA - Brian ---------------------------------------------------------------------- >Comment By: Kevin Downs (kdowns) Date: 2005-04-15 01:15 Message: Logged In: YES user_id=919791 The linearity problems do not make any really significant differance unless the projects are at least 5000 topics; for your project size they are negligable, so splitting things up will not help... 10 mins does seem excessive for 3000 topics. fyi, here are some ball-park figures for NDoc 1.3.1 on my test machine (800MHz PIII, 384Mb, XP Pro). (system.drawing) ~2800 pages ==> 5 minutes (system) ~5400 topic pages ==> 11 minutes Of course, these figures are with no other processes running. NDoc is CPU and I/O heavy, so if there is another process is using large chunks these resources then things will slow down alarmingly! If you have checked your disk defrag status, and the anti- virus config, then I would suggest monitoring the machine while NDoc is running. For a first attempt, task manager will probably do; just check if any other processes are consuming significant cpu or performing a lot of i/o.... ---------------------------------------------------------------------- Comment By: Brian (brisls1) Date: 2005-04-14 23:28 Message: Logged In: YES user_id=1231798 Close to 3000 files in my MSDN folder. NDoc version is 1.3.1792.0 .Net Framework v1.1.4322 Documentation Type is MSDN with Output Target = HTML HELP Would I benefit from separate smaller NDoc projects? Still would need the same number of classes doc'd. THX ---------------------------------------------------------------------- Comment By: Kevin Downs (kdowns) Date: 2005-04-14 18:38 Message: Logged In: YES user_id=919791 It difficult to give specific advice without knowing how many topic pages are being generated and the speed/workload on the server.... In current NDoc releases, performance degrades as the size of the project increases, though this is generally only a problem for large projects (>500 topics). In the next release, the MSDN \ VS.NET documenters are being redesigned to make document production scale more linearly. General Tips 1. Ensure the disks are kept well-defrag'ed. With the number of seperate files NDoc is generating, disk performance can have a significant impact. 2. If possible, ensure that anti-virus checking is not taking place on the output path. AV software can chew-up a large chunk of CPU time scanning the NDoc output during topic creation and when the help compiler is operating... ---------------------------------------------------------------------- Comment By: Kevin Downs (kdowns) Date: 2005-03-04 14:53 Message: Logged In: YES user_id=919791 How many pages are you generating? ---------------------------------------------------------------------- Comment By: Brian (brisls1) Date: 2005-03-04 06:16 Message: Logged In: YES user_id=1231798 Using Version 1.3 i.e. C:\Program Files\NDoc 1.3\bin\net\1.1\NDocConsole.exe Running on Windows Server 2003 Using the C# documenter Documentation Type is MSDN with Output Target = HTML HELP HTH- Brian ---------------------------------------------------------------------- Comment By: Kevin Downs (kdowns) Date: 2005-03-04 06:04 Message: Logged In: YES user_id=919791 A bit more info would be helpfull... What version number of NDoc are you using? What framework version are you using? Which documenter are you using? How many pages are you generating? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=416079&aid=1155925&group_id=36057 |