[Info-vax] Lock rates
Hein RMS van den Heuvel
heinvandenheuvel at gmail.com
Mon Nov 9 17:46:04 EST 2020
On Monday, November 9, 2020 at 2:47:10 PM UTC-5, Stephen Hoffman wrote:
> On 2020-11-09 19:17:23 +0000, Rod Regier said:
>
> > Just confirming that on a non-cluster node w/proper AUTOGEN tuning that
> > I don't need to worry about large lock rates that appear in concert
> > with large direct I/O rates.
> Does your performance data show that your app is meeting your current
> performance requirements
Yup, as Hoff asks and answers.
Now if there is a suggestion of a problem then we'll need much more info.
Alpha or Itanium?1 Cpu? 2? 16? -
If more than 4 cpus and there are lock management suspicions , did you try the dedicated lock manager?
What is the order of magnitude of what you perceive as large?
10,000/sec ? walk in the park!
50,000/sec ? It's getting busy
100,000/sec ? Starting to be worrisome
150,000/sec ? Boy you do have a nice fast CPU going, but it is maxing out on the lock management.
.
Lock management overload would likely show as high MPsync time, in which case a dedicated lock manager CPU may help to use that wasted (mpsync) time more effectively.
fwiw - RMS will typically do at least one often more locks per direct IO on a shared files.
The core (VBN) lock to be one to protect others from reading updated data while in transit.
Cheers,
Hein
More information about the Info-vax
mailing list