[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Activity: Performance Indicators - Latch timeouts

  • Thread starter George Potemkin
  • Start date
Status
Not open for further replies.
G

George Potemkin

Guest
Just run a quick “tranprobe” test. It’s Tom’s readprobe test but the readalot.p is replaced by: DISABLE TRIGGERS FOR LOAD OF customer. DEFINE VARIABLE i AS INTEGER NO-UNDO. REPEAT TRANSACTION: DO ON ERROR UNDO, LEAVE: CREATE customer. DELETE customer. END. END. It’s the most aggressive transactions in Progress. The box: NumCPU = 96 The sparcv9 processor operates at 1165 MHz (yes, it’s 10 times slower than the modern CPUs) Result: MTX locks reached approximately 200,000 locks per sec, 530 naps per sec at 15 users and ~ 230,000 locks per sec, 2,600 naps per sec at 100 users. MTX latch was busy almost 100% of the time. Only 70% of sessions opened the simultaneous transactions. Transactions were in ACTIVE phase only 15-20% of the time, “Phase 2” – 50%, BEGIN – 33%, None -1.5-3%. See MTX.xlsx (Please visit the site to view this file)

Continue reading...
 
Status
Not open for further replies.
Top