Hi Siva Kumar -
Here are my thoughts about your post and map tuning in general.
First, I would start with some basic questions such as:
- How often will the map be executed?
- How important is performance?
- Will there be competition for resources?
And then some application specific questions:
- What is the nature of the inputs and outputs?
- Is there a typical size or size range?
- Is the size consistent or variable?
- Are there looping structures or hierarchy?
- How complex are the mapping requirements?
- Are inputs being combined?
- Are there multiple outputs?
- Are any of the outputs used as inputs for subsequent outputs?
- What are the expected commit/rollback requirements?
You've said that the input to your map is formatted as JSON, your output is a flat file, and both are very large. That's not a lot to go on but it does lead me to suggest that you look for ways to break the input into smaller chunks that can be used to generate chunks of output. Going down that path will require analysis and additional development effort up-front but should allow for better performance and resource utilization.
If you'd like to provide more information about your specific requirements either in this forum or via e-mail, I should be able to go a bit further with recommendations.
Regards,
Kristen Stenberg
Senior Integration Consultant at CoEnterprise
P 973-769-6950 | E
kristen.stenberg@coenterprise.com------------------------------
Kristen Stenberg
------------------------------