Data Anomalies on DS 5.2 - large allocation for small # of entries

Question

I have 2 DS 5.2 systems running on Red Hat ES 3.
These systems have only 1.5 million entries , yet are using
over 16G of storage . Recently we had 200k were of updates,
and added almost 2G worth of storage. Read performance is excellent,
adds / updates extremely poor , taking almost 1 second/ add using
java. The actual data per entry is small , less than 200 bytes.
I am not responsible for the organization of the data, but suspect -
from experience Oracle and Sybase - that the data is not organized
correctly, or we need to do data maintenance, such as dropping
and recreating indexes.
Where can I find heuristics or documentation on these issues ? I know the devil is the details, but the current system does not feel 'right'.
Any help gratefully accepted,
JYard
UCLA

Answer 1

If you have too many unneeded indexes, especially substring indexes, you will use a lot of extra disk space. Also, maintaining these indexes will impact write performance for sure. You should make sure that you have all the indexes you need, but ONLY the indexes you need.
Eric