text: Consider the following suggestions: 
  
  (cid:2) Best results can be achieved if the data compression ratio stays at 25% or more. Volumes 
  can be scanned with the built-in Comprestimator utility to support decision if IBM Rational 
  Team Concert™ is a good choice for the specific volume. 
  
  (cid:2) More concurrency within the workload gives a better result than single-threaded 
  sequential I/O streams. 
  
  (cid:2) I/O is de-staged to RACE from the upper cache in 64 KiB pieces. The best results are 
  achieved if the host I/O size does not exceed this size. 
  
  (cid:2) Volumes that are used for only one purpose usually have the same work patterns. Mixing 
  database, virtualization, and general-purpose data within the same volume might make 
  the workload inconsistent. These workloads might have no stable I/O size and no specific 
  work pattern, and a below-average compression ratio, which makes these volumes difficult 
  to investigate during performance degradation. Real-time Compression development 
  advises against mixing data types within the same volume whenever possible. 
  
  (cid:2) It is best to not recompress pre-compressed data. Volumes with compressed data should 
  stay as uncompressed volumes. 