Originally posted by: jvanboga
Curious, how big is big? For us a large hipaa file is 75 - 100 mb. We can read, map and load a 100 mb hipaa transaction into 13 oracle tables in less than 10 minutes. That includes post mapping edit processes.
You've already stated that you've turned off map logs and traces so...
Performance enhancers can depend on the environment. For example, if you allow Windows to manage disk memory on the fly performance can be negatively impacted. I have found that our maps run faster when you preallocate space.
They can also be impacted by type tree design. Unfortunately, with hipaa files you want a certain level of validation going on when you read the file or you run the risk of having data integrity problems. We have historically used the type-1 hipaa trees which, for the most part only validate structure. They do not, for example check the punctuation of an SSN.
As stated above, using burst mode can really help giving you a speed boost if the tree is designed properly. If not, burst will add little to performance. Historically the hipaa pack type trees have been pretty well designed.
Map design/structure will affect your performance as well. Poorly structured maps can really suck up resources and negatively affect your processing time. You can prove this by designing a map two different ways, run each and watch what happens to your temp files.
Playing with pagesize/count settings can help boost performance as well. I've found there isn't a single best way to configure this. You have to play with it.
Usually, I don't see a benefit between 'create' and 'reuse' but others seem to.
Are you reading any DB data in your map?
#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender#DataExchange