Actually I have a huge document (Approx 500 pages document) and it is taking approx. 2 minutes to load the whole cycle of transformation tables. Is there anyway to reduce the timing for the whole load cycle of transformation tables. Please note, the input I am using is XML.
Without seeing the data and the xychange tables, its difficult to provide any advice. However, usually the biggest performance hits in xychange are when there is a * wildcard at the beginning of a rule. Another hit can be when using reinput.
For this group to provide help, you need to show examples of what you're trying to do with xychange - and better yet, explain why you're using xychange with XML. If its just character replacement then xychange should be faster than XSLT or similar. But if you're moving attributes and/or elements around then XSLT would probably be faster/easier/better.
PS For those that knew Larry Liebson's mantra: I didn't say it was cheaper - so "Liebson's Law of 'pick 2'" still holds true.
Without seeing the data and the xychange tables, its difficult to provide any advice. However, usually the biggest performance hits in xychange are when there is a * wildcard at the beginning of a rule. Another hit can be when using reinput.
For this group to provide help, you need to show examples of what you're trying to do with xychange - and better yet, explain why you're using xychange with XML. If its just character replacement then xychange should be faster than XSLT or similar. But if you're moving attributes and/or elements around then XSLT would probably be faster/easier/better.
PS For those that knew Larry Liebson's mantra: I didn't say it was cheaper - so "Liebson's Law of 'pick 2'" still holds true.
Translate
