Cisco Cisco Tidal Enterprise Scheduler 6.2 Brochure
31
Cisco Tidal Enterprise Scheduler 6.2 Performance Tuning Guide
OL-32251-01
Cisco Tidal Enterprise Scheduler 6.2 Performance Tuning Guide
Size-Based Guidelines for Tuning Your Environments
jobid >=1002 and jobid <= 2002
jobid >=2003 and jobid <= 3003
…
If all the job IDs are sequential and start at 1, then each batch request will result in roughly 1000 records.
However, if there are large gaps in the job IDs, due to mass job deletes for example, the request may
return fewer results depending on where the job record ID falls in that range. While executing the read
and running Transporter in the debug mode, if you find that very few or 0 records are returned given a
READ_BATCHES configuration, then increasing this value will be necessary to reduce the number of
requests that return 0 or few results.
However, if there are large gaps in the job IDs, due to mass job deletes for example, the request may
return fewer results depending on where the job record ID falls in that range. While executing the read
and running Transporter in the debug mode, if you find that very few or 0 records are returned given a
READ_BATCHES configuration, then increasing this value will be necessary to reduce the number of
requests that return 0 or few results.
Note
This approach appears to be more beneficial when there are many job records (50K or more).
READJOBS_ALL
READJOBS_ALL reads all jobs based on the first and last job ID. The result is that all jobs will be read
in a single request. This approach is different from the job.getList call in that while both return all jobs,
this request adds a query condition to the request, which seems to produce better performance. However,
because all records are returned in a single request, the Client Manager will need to process all the
records to send to Transporter.
in a single request. This approach is different from the job.getList call in that while both return all jobs,
this request adds a query condition to the request, which seems to produce better performance. However,
because all records are returned in a single request, the Client Manager will need to process all the
records to send to Transporter.
Note
If there are many job records, the overhead on the Client Manager may be too high.
General Best Practices
Consider the following best practices while using the Transporter:
•
Use server-side filter to read specific jobs.
•
Run only one instance of transporter at a time in a machine.
•
Have less number of top level groups.
•
Transport during off peak hours or when client manager usage is significantly less.
Size-Based Guidelines for Tuning Your Environments
Small, medium, and large configurations require parameters to be tuned differently. Set the parameters
as indicated in this section.
as indicated in this section.
Small Configuration
tes-6.0.0.0.dsp
CacheSynchronizer.NumThreads=2
DataCache.ReadConnectionsMin=5
DataCache.ReadConnectionsMax=10
DataCache.WriteConnectionsMin=5
DataCache.WriteConnectionsMax=10