Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Doug Fossmeyer — — source: Informix-list mailing list archive (1991-1998)
Hello all,
I am hoping you can clear up something for me. I am curious about the
onstat -P command. The Admin Guide/Manual for 7.3x has one pithy statementabout "display for all partitions the partition number and break up of pages
in the buffer pool belonging to the partition". I assume the values are 2k
pages. I realize I can map backwards the partnum to the index and data that
resides in the buffers at that point in time. Implying that the tables with
continuously high index or data would be good candidates for placing into
memory (as long as it doesn't cause paging).
Of what value and interpretation are the last four lines of summary data:
data, btree, other percentages? I assume that it tells me how much of the
index vs. data is buffered in memory and would be very useful if I decided
to pin tables and indexes into memory.
Is there a data/btree ratio that is recommended. We are always at a 70/30
data/index ratio.
tia
Doug
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.