This content has been marked as final. Show 2 replies
although custom code (validators, methods, guard conditions, etc) may negate this, we recommend no app pool recycling. app pools should be monitored for memory use, and at a minimum; GSM, GSMView, and NPD should be in their own app pools. After that, the app pool settings as outlined in the 6.1 install/upgrade guide (and reiterated in the 126.96.36.199 Maintenance Pack Install Guide) should be followed.1 person found this helpful
Keep in mind, on a 32-bit server, anything above ~800 MB in any given app pool will have adverse affects on performance and functionality. On a 64-bit server, this is raised to ~1800 MB.
We are currently working on a capacity planning guide that will outline this information and more. In it, we have defined an app pool distribution that serves as a good starting point. However, every customer is different, so this should be modified based on your environment and needs.
|App Pool Name |Applications|
|PLM4P_PDM |Integration, ProdikaReporting, SCRM, WFA|
|PLM4P_MAIN |Portal, REG, UGM, DRL|
|PLM4P_FC |PQS, OPT|
|PLM4P_COLLAB|SupplierPortal, SupplierPortalAdmin, eQ|
App Pool Settings posted for quick reference (however, the latest install guide on OTN should always be referenced for the latest settings)
|IIS 7.x Parameter|Parameter Value|
|Enable 32-Bit Applications|True|
|Managed Pipeline Mode|Classic|
|Identity (Custom Account)|PLM4P_AppUser|
|Regular Time Interval|0|
Thanks! We have our App Pools set as follows and we set all other settings as outlined in the install guide, except for the recycling. Which now is set not to recycle.
App Pool Name Applications
PDM_GSM GSM, GSMView
PDM_Global cssPortal, drl, eq, integration, pqs, reg, ProdikaReporting, SCRM, SupplierPortalAdmin, SupplierPortal, ugm, WebDAV, wfa
We also have separate server for NPD vs GSM with same app pools.
Please let us know when the capacity planning guide is released.