Recent content by pinne65

Thanks - restart it is then. Will investigate 11.7

Ran into a pickle - added - SQLWidthUpdate ON in on a 11.6 database and having some performance issues. Reading that it should be possible to update the parameter with the database online: Progress Documentation using either promon or _DbParams VST. I'm not seeing option 16 - adjust startup...

BINGO! ----- Locks ----- ------ Busy ------ Naps ---------- Spins ----------- ----- Nap Max ----- Owner Total /Sec /Sec Pct /Sec /Sec /Lock /Busy Total HWM 04/13/18 20:00:02 OM --...

That makes me feel better. I had a hunch, just waiting for the right opportunity to restart.....

Yep fewer than 3072: select count(*) from _storageobject 2,623 However, R&D 1|13 Primary object cache (-omsize): Total: 1024 Used: 1024 Pinned: 0 Secondary object cache (-omsize): Total: 3072 Used: 1051 Pinned: 0 I didn't restart, just upped the size online, but omsize startup parameter...

Ok - here are the results. Not much of a difference. But I learned a lot in the process and will continue the tuning quest one step at a time.

Wheeew - Thanks! I would hate to find that out the hard way.

Thanks again guys! I'm just holding off so I can gather more stats. (Didn't know about the hidden menu last week so I had to revise my collection script). I should have 24 hours worth by 12pm today. So I will make the change then. And go from there.

Continuing this thread in OE and SQL tuning parameters (-omsize in particular)

This is a continuation of Answered - Can (SQL) UPDATE STATISTICS hamper performance of ABL AFTER the fact - NO! that took a new direction. Current omsize is 1024, database objects are 2623. Below are samples from protop and promon for approximately the same 60s interval. Protop...

Will have to get back on this - will probably need to run for at least a few hours with normal load Deng - I was thinking omsize was the magic bullet :-). Will check protop also next week for sure

I agree - my original question has been answered. I wish there was a way to split the thread and create a new one from below the 1st 3rd of the original posts.

Thanks again Rob! I'm running it on Linux.

Been gathering stats from promon r&d activity since yesterday and was about up the omsize. But it doesn't seem like there's a need, or?: Been running gus's test script from 11.3.2: default -omsize & high number of MTL_OM latches - Forum - OpenEdge RDBMS - Progress Community and I don't see any...

Hello, I'm on OE 11.6 / RHEL 5.11 so it might be different but I'm Just curious of the command line arguments you are using for promon in the original post. I haven't been able to find any documentation on promon's command line arguments. Looking at promon, it passes the argumenst to _mprshut...