G
gus
Guest
For the most part, there is not much you can do about semaphore waits /except/ reduce the record lock conflicts in the application. semaphore activity isn't a terribly useful metric anyway (it only tells you that somebody was blocked and had to wait for /something/). pay no attention. look at the resource waits instead. -- regards, gus (gus@progress.com) "If I set here and stare at nothing long enough, people might think I'm an engineer working on something." -- S.R. McElroy > On Dec 22, 2015, at 6:25 AM, dianne.evans@danwood.co.uk wrote: > > Update from Progress Community [https://community.progress.com/] > > dianne.evans@danwood.co.uk [https://community.progress.com/members/dianne.evans_4000_danwood.co.uk] > > Following on from a colleague's recent question on our recurring database crashes due to Semaphores: > > I was wondering if people could assist with what a typical range of semaphore-wait should be, in "normal" behaviour. > > Our DB has been up for about a week now, and looking in PROMON R&D section, I can see the following values. > > 12/22/15 Activity: Other > 11:16:21 12/15/15 12:37 to 12/22/15 11:12 (166 hrs 34 min) > > Total Per Min Per Sec Per Tx > > Commit 44492519 4452 74.20 1.00 > Undo 247015 25 0.41 0.01 > Wait on semaphore 376256 38 0.63 0.01 > Non-blocking waits 25 0 0.00 0.00 > Semaphore latch waits 43765 4 0.07 0.00 > Flush master block 2097 0 0.00 0.00 > > Can anyone say whether the values of wait-on-semaphore = 38 per minute, or the semaphore-latch-waits of 4 per minute are OK, or extreme? > > The above is taken from our Live database, but for the last two days, both of our test databases (copies of live) have suffered similar semaphore problems. > > Any pointers would be a great help > > View online [https://community.progress.com/community_groups/openedge_general/f/26/t/22128] > > You received this notification because you subscribed to the forum. To stop receiving updates from only this thread, go here [https://community.progress.com/community_groups/openedge_general/f/26/t/22128/mute]. > > Flag [https://community.progress.com/community_groups/openedge_general/f/26/t/22128?AbuseContentId=45ea083a-f4f9-4dec-a1a2-f855c1f77fda&AbuseContentTypeId=46448885-d0e6-4133-bbfb-f0cd7b0fd6f7&AbuseFlag=true] this post as spam/abuse.
Continue reading...
Continue reading...