Hi All,
This topic isn't really regarding an error, but best practice. Is there any magical number of lookups you can do in one transformer before you should use a second tranformer? Is there a performance difference between doing 20 lookups in one transformer and 10 lookups each in 2 transformers for example? Is it all relative?
Thanks
Maximum Number of Lookups in single transformer
Moderators: chulett, rschirm, roy
Really depends, as you said, its relative. If having 20 lookups does not slow down the job, then go for it. Else I would recomend doing it in two seperate jobs.
Like, keeping 5 heavy lookups in one job and 15 small lookups in another job.
This will also help you in restratability.
Like, keeping 5 heavy lookups in one job and 15 small lookups in another job.
This will also help you in restratability.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 36
- Joined: Mon Jul 16, 2007 3:37 am
- Location: USA
Re: Maximum Number of Lookups in single transformer
Hi,jpr196 wrote:Hi All,
This topic isn't really regarding an error, but best practice. Is there any magical number of lookups you can do in one transformer before you should use a second tranformer? Is there a performance difference between doing 20 lookups in one transformer and 10 lookups each in 2 transformers for example? Is it all relative?
Thanks
U try to use less than or equal to 7 lkp ups on a single transformer,else u r performance will go down..if u need to take more than 7 tkae them in another transformer.
VINOD
There is no particular reason for '7' references. What I will do with a particularly complex transform stage on a multi-cpu system is monitor the %CPU of that tranform stage. If it is close to 100% then the job can be made somewhat faster by splitting into 2 transforms stages (assuming interprocess buffering being enabled). This splitting can be continued until CPU use on a single transform is no longer the bottleneck. Note that the procedure applies in similar fashion to both server and PX jobs.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>