G
George Potemkin
Guest
Thanks, Dapeng! BTW, in the Sequence Readprobe tests under V11.6 it's turned out that the bottleneck is TXQ latch instead of BUF latch as I did expected. The number of their locks are, of course, the same. BUF latch had up 250 naps/sec while TXQ latch only 100-150 naps/sec.BUF latch is an aggregator for the multiplexed latches but during the tests all sessions read the only block - the sequence block and it's not on LRU chain (the -lruskips will not help in this case). But a lock duration of the TXQ latch seems to be (a bit?) longer than of the BUF sub-latches (latObjLatchLock). Test environment: Old Solaris box 2 physical processors (sparcv9 1165 MHz), 112 virtual processors. Memory size: 32544 Megabytes Progress version: 11.6.1
Continue reading...
Continue reading...