Why would you disable transformers when measuring reader performance?

Why would you disable transformers when measuring reader performance?

• A. To ensure only reader processing time is measured.
• B. To prevent the workspace from running.
• C. To cause the log to update more slowly.
• D. To avoid timing the transformers.

Answer: (A)

Measuring reader performance aims to isolate the time spent reading data from any downstream processing. If transformers are running, their own processing adds overhead—time spent transforming, filtering, and routing features—which would skew the measurement and make it look like the reader took longer than it actually did. By disabling transformers, you prevent that extra work from happening, so the elapsed time more accurately reflects only the reader’s activity as it reads features from the source. This gives a true measure of how fast the reader itself performs, independent of the transformation steps that would normally follow.

Measuring reader performance aims to isolate the time spent reading data from any downstream processing. If transformers are running, their own processing adds overhead—time spent transforming, filtering, and routing features—which would skew the measurement and make it look like the reader took longer than it actually did. By disabling transformers, you prevent that extra work from happening, so the elapsed time more accurately reflects only the reader’s activity as it reads features from the source. This gives a true measure of how fast the reader itself performs, independent of the transformation steps that would normally follow.