DataLoader/MX Reference Manual (G06.24+)

Running DataLoader/MX
DataLoader/MX Reference Manual—525872-002
3-15
Analyzing Your Configuration
For most configurations, the statistics provided through the -S= parameter should be
sufficient. However, you can also use Measure and other performance tools.
When you run DataLoader/MX with the -S= parameter, it generates statistics about the
internal buffer pool. DataLoader/MX uses this pool to buffer data for the downstream
reader processes (typically other DataLoader/MX processes). When a DataLoader/MX
process uses $RECEIVE as its output, it reserves 16 buffers to block the records for up
to 16 different reader processes. When all buffers are full and no reader has appeared,
the initial DataLoader/MX must stop processing data until at least one buffer is freed
up.
Use DataLoader/MX statistics for the buffer pool for a good indication of how well
balanced the configuration is:
•
If the buffer pool is full most of the time, you might not have enough downstream
DataLoader/MX processes to consume the data at the rate the initial
DataLoader/MX is generating it. You might want to increase the number of
downstream DataLoader/MX processes to the point at which the consumer rate is
as high as or higher than the production rate.
•
If the buffer pool is empty most of the time, the downstream processes are running
ahead of the initial DataLoader/MX process. You might want to consider shifting
some work from this DataLoader/MX process to the downstream DataLoader/MX
processes.
A well-designed loading application uses the smallest number of processes required to
accomplish the loading task and distributes the load evenly across all available CPUs.
See Section 6, DataLoader/MX Examples for examples of creating and maintaining
parallelism within the four basic loading scenarios.