fully applied to
between 50 and 100 databases without issues. However, we have recently
encountered an issue related to LWLocks contention.
The problem happened during the taking of an initial snapshot of a slightly
bigger database, approximately 500GB, with a single table accounting for
300GB. Althoug
On Mon, Apr 25, 2022 at 10:33 AM Michael Lewis wrote:
>
> On Thu, Apr 21, 2022 at 6:17 AM Chris Bisnett wrote:
>>
>> We're working to update our application so that we can
>> take advantage of the pruning. Are you also using native partitioning?
>
>
> No partitioned tables at all, but we do have
On Thu, Apr 21, 2022 at 6:17 AM Chris Bisnett wrote:
> We're working to update our application so that we can
> take advantage of the pruning. Are you also using native partitioning?
>
No partitioned tables at all, but we do have 1800 tables and some very
complex functions, some trigger insanity
> We are occasionally seeing heavy CPU contention with hundreds of processes
> active but waiting on a lightweight lock - usually lock manager or buffer
> mapping it seems. This is happening with VMs configured with about 64 CPUs,
> 350GBs ram, and while we would typically only have 30-100 concu
We are occasionally seeing heavy CPU contention with hundreds of processes
active but waiting on a lightweight lock - usually lock manager or buffer
mapping it seems. This is happening with VMs configured with about 64 CPUs,
350GBs ram, and while we would typically only have 30-100 concurrent
proce
