Document block commit size tuning procedure

[GoogleCodeExporter]

1. To which tool/application/daemon will this feature apply?

Replicator applier.

2. Describe the feature in general

Describe how to use & interpret 'trepctl -service X status -name tasks' command 
to tune blockCommitRowCount parameter.

3. Describe the feature interface

Doc page.

4. Give an idea (if applicable) of a possible implementation

5. Describe pros and cons of this feature.

5a. Why the world will be a better place with this feature.

Allows to help users more easily and know-how is not forgotten.

5b. What hardship will the human race have to endure if this feature is
implemented.

Increased doc size.

6. Notes

See case #1055 for details of tuning.

Original issue reported on code.google.com by linas.vi...@continuent.com on 21 Aug 2013 at 3:12

[GoogleCodeExporter]

Original comment by linas.vi...@continuent.com on 26 Aug 2013 at 1:54

• Added labels: FixedIn-2.1.3
• Removed labels: FixedIn-2.1.2

[GoogleCodeExporter]

There won't be a 2.1.3.

Original comment by linas.vi...@continuent.com on 17 Sep 2013 at 10:13

• Added labels: fixedin-2.2.0
• Removed labels: FixedIn-2.1.3

[GoogleCodeExporter]

This is documented here: 

http://docs.continuent.com/tungsten-replicator-2.2/performance-block.html

and 

http://docs.continuent.com/tungsten-replicator-2.2/performance-block-monitor.htm
l

Original comment by mc.br...@continuent.com on 23 Dec 2013 at 10:45

• Changed state: Fixed