D
dbeavon
Guest
I found some low hanging fruit.... I found this one after coming to the conclusion that my only real bottleneck in the database seems to be latch timeouts: (Found via checking promon/R&D/deghb): 3/1. Activity: Performance Indicators So I changed -spin from 2000 to 500000 and my commits per second are now in the 300-500 range (instead of 100 before). And better yet, I'm actually seeing some disk utilization in glance! I wish OE would auto-tune the spin. This seems like an especially obscure thing for the average OE DBA to be responsible for. The CPU usage is still under 10% for this entire team of processes. Not sure why our we always used -spin 2000 by default. Maybe it is the best-practice from a decade ago.
Continue reading...
Continue reading...