Basically lruskips just keeps the DB from moving the block to the top of the MRU list every time the block is accessed. Instead a less expensive counter is maintained and when that counter is reached it will move the block to the top of the MRU list. The idea is that if you are hammering the same blocks (common data/index entries) you can get an improvement since the MRU/LRU list can only maintained by one connection at a time.
So I guess what I am struggling with is that no block in our buffer pool appears to ever make it off the LRU list onto our MRU list, given our current settings:
First, our latch timing and activity is disabled which leaves us lacking some data.
Spin timeouts is 100000, I believe much too high for our environment. 10,000 is a better adjustment and probably lower is optimal
♀10/24/14 OpenEdge Release 11 Monitor (R&D)
06:27:34 Adjust Latch Options
1. Spins before timeout: 100000
2. Enable latch activity data collection
3. Enable latch timing data collection
4. Initial latch sleep time: 10 milliseconds
5. Maximum latch sleep time: 250 milliseconds
6. Record Free Chain Search Depth Factor: 5
7. Enable LRU2 alternate buffer pool replacement policy
8. Adjust LRU force skips: 100
9. Adjust LRU2 force skips: 0