Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
Performance of Regenerate All By PT
System
This implementation has a custom menu item that regenerates all pages generated with a given PT. There is a performance problem with this CMI that appears to be related to scanning the Interwoven filesystem and executing iwextattr for each html file, iwregen for each match. I am not sure but it seems like performance would be better (one less fork) if the script called iwpt_compile.ipl directly (since I imagine iwregen is just calling iwpt_compile.ipl without adding much value, probably after checking extended attributes again and maybe even parsing templating.cfg). Best would be if the functionality of iwpt_compile.ipl was in a module so I could call the function instead of forking iwpt_compile.ipl, but really I think the problem is with the scan, not the generate (since there are not too many pages generated from each PT).
Is there any other way to improve the performance? I was thinking of storing a list of the files generated from each PT somewhere (in a file, as extended attributes on the PT, in a database, etc.) so it wouldn't have to run iwextattr for each file, but that would be customization I would prefer to avoid if possible.
The script is pretty basic but I don't think I can post it. Just looking for general performance suggestions specific to the problem of regenerate.
Find more posts tagged with
Comments
There are no comments yet