Conversion Following a few The settings of Word Automation Services can easily be set items begin to simple rules can to push the service past its practical limits. Doing so will fail more often help correct or likely result in: after changing prevent either of Less overall throughput the settings the previously for Word listed symptoms: Conversion items will fail more often Automation Never set Total Services Active Conversion Processes to be more than N-1 where N is the number of processing cores of the application server. Also, never set Number of conversions to start (per conversion process) to be greater than what is suggested in for the desired output formats unless Frequency with which to start conversions (minutes) is also adjusted (in direct proportion) such that the resulting throughput target remains the same. Other services An active conversion process will at times fully leverage a A few things can begin to be processing core on the application server. An application server be done to less configured as recommended in may thus use almost the entire decrease the responsive CPU at any given time given that the Word Automation Services impact of Word after changing timer job also runs on its own core periodically. Automation the settings Services on other So, if other services such as Microsoft Office Excel or Microsoft for Word services: Office Web Apps (for example) require CPU resources from such an Automation application server then there might be an undesirable wait time 1) Throttle down Services that results in increased perceived latency for those other services. the Total Active Conversion Processes for Word Automation Services, perhaps to the level recommended in . 2) Add additional
Conversion items begin to fail more often after changing the settings for Word Automation Services The settings of Word Automation Services can easily be set to push the service past its practical limits. Doing so will likely result in: Less overall throughput Conversion items will fail more often Following a few simple rules can help correct or prevent either of the previously listed symptoms: Never set Total Active Conversion Processes to be more than N-1 where N is the number of processing cores of the application server. Also, never set Number of conversions to start (per conversion process) to be greater than what is suggested in for the desired output formats unless Frequency with which to start conversions (minutes) is also adjusted (in direct proportion) such that the resulting throughput target remains the same. Other services begin to be less responsive after changing the settings for Word Automation Services An active conversion process will at times fully leverage a processing core on the application server. An application server configured as recommended in may thus use almost the entire CPU at any given time given that the Word Automation Services timer job also runs on its own core periodically. So, if other services such as Microsoft Office Excel or Microsoft Office Web Apps (for example) require CPU resources from such an application server then there might be an undesirable wait time that results in increased perceived latency for those other services. A few things can be done to decrease the impact of Word Automation Services on other services: 1) Throttle down the Total Active Conversion Processes for Word Automation Services, perhaps to the level recommended in . 2) Add additional
WASCapacityPlanningDoc.docx