makes the most sense to you.
Textual ETL is sensitive to resource consumption. In general, textual ETL operates in an
efficient manner. The only things to be avoided are the following:
Looking for more than four or five proximity variables. It is possible to swamp textual ETL by looking
for many proximity variables.
Looking for many homographs. It is possible to swamp textual ETL by looking for more than four or five
homograph resolutions.
Taxonomy processing. Loading more than 10000 words in a taxonomy can slow the system down.
Date standardization. Date standardization causes the system to use many resources. Do not use date
standardization unless you really need to use it.Chapter 10.2: Mapping