What does it get better performance? Filter or transformer?

[manuel.gomez]

I have found this reading some Ascential documentation:

Transformer constraints are FASTER than Filter stage!
Filter constraints are interpreted

Is it true? I have always tryed to avoid transformers and using filter stages instead, but now it seems that transformer is better!

[ArndW]

I would test this empirically before taking the documentation's word for it.

[mdan]

I have found this reading some Ascential documentation:

Transformer constraints are FASTER than Filter stage!
Filter constraints are interpreted

Is it true? I have always tryed to avoid transformers and using filter stages instead, but now it seems that transformer is better!

Yes, at least for 7.5.2 transformer is faster. You may use transformer unless the special situation when the column that you filter by should be defined (parameter) at the runtime.

[John Smith]

I have found this reading some Ascential documentation:

Transformer constraints are FASTER than Filter stage!
Filter constraints are interpreted

Is it true? I have always tryed to avoid transformers and using filter stages instead, but now it seems that transformer is better!

Don't be overly concerned which one has better performance, I think it's safe to use both and if you job is written properly both stages will perform satisfactorily.

[sreddy]

Hi

That is quite natural, we can do
1. Filter the data (Constraint)
2. Do conversions
3. We can create Surrogate Key
So many things we have to do. That is why performance is low.

Filter stage is specified only for that purpose

http://it.toolbox.com/blogs/infosphere/ ... -evil-9801

I have found this reading some Ascential documentation:

Transformer constraints are FASTER than Filter stage!
Filter constraints are interpreted

Is it true? I have always tryed to avoid transformers and using filter stages instead, but now it seems that transformer is better!

[chulett]

http://it.toolbox.com/blogs/infosphere/ ... -evil-9801

Ah yes, a Vincent blog.

Keep in mind the fact that his observations are just over two years old now and - from what I understand - the stage has since been vindicated, rewritten to dramatically improve its speed.

[vmcburney]

I would avoid the filter stage - it's not as user friendly as a Transformer and you are likely to be using your Transformer for multiple things. The one time I found a filter stage shaved about 5% off my job run time was when I was filtering out over 75% of the incoming rows and feeding the data to a Transformer with a lot of transformation logic. The Filter stage avoided a lot of unneccessary transformations - but then maybe two Transformers in a row would have been even faster.

[John Smith]

Hi

That is quite natural, we can do
1. Filter the data (Constraint)
2. Do conversions
3. We can create Surrogate Key
So many things we have to do. That is why performance is low.

Filter stage is specified only for that purpose

http://it.toolbox.com/blogs/infosphere/ ... -evil-9801

I have found this reading some Ascential documentation:

Transformer constraints are FASTER than Filter stage!
Filter constraints are interpreted

Is it true? I have always tryed to avoid transformers and using filter stages instead, but now it seems that transformer is better!

The reference to that blog is dated 2006 and we're halfway through 2008. come on that information is already dated and you should have some faith that IBM has done some work with the product during all that time. Don't think they pay their developers to sit idle...