R
Richard Banville
Guest
Good point on the buffer lock queue. I’ve seen situations where the sequence block access becomes a bottle neck for insert intensive applications when conflicts arise with other parts of the app checking the current sequence value or performing other sequence requests.. _________________________________ Richard Banville Fellow, OpenEdge Development 14 Oak Park | Bedford, MA 01730 | USA DIRECT +1 781 280 4875 richb@progress.com From: George Potemkin [mailto:bounce-GeorgeP12@community.progress.com] Sent: Monday, May 04, 2015 10:02 AM To: TU.OE.RDBMS@community.progress.com Subject: RE: [Technical Users - OE RDBMS] Controls to help high demand for record create RE: Controls to help high demand for record create Reply by George Potemkin Check: promon/R&D/1/4/2. Status: Blocked Clients promon/R&D/debghb/6/15. Status: Buffer Lock Queue Take a few snapshorts and check if the same block(s) is mentioned on the few screens. Most likely the bottleneck is an root block of some index. Anyway check if promon reports any dbkeys from the list cretated by ObjectInfo.p: ftp.progress-tech.ru/.../ObjectInfo.p Regards, George Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...