On 07/11/2024 14:24, Li, Yunxiang (Teddy) wrote:
[Public]
From: Tvrtko Ursulin
Sent: Thursday, November 7, 2024 5:48
On 31/10/2024 13:48, Li, Yunxiang (Teddy) wrote:
[Public]
From: Christian König
Sent: Thursday, October 31, 2024 8:54 Am 25.10.24 um 19:41 schrieb
Yunxiang Li:
Before, ev
[Public]
> From: Tvrtko Ursulin
> Sent: Thursday, November 7, 2024 5:48
> On 31/10/2024 13:48, Li, Yunxiang (Teddy) wrote:
> > [Public]
> >
> >> From: Christian König
> >> Sent: Thursday, October 31, 2024 8:54 Am 25.10.24 um 19:41 schrieb
> >> Yunxiang Li:
> >>> Before, every time fdinfo is quer
On 31/10/2024 13:48, Li, Yunxiang (Teddy) wrote:
[Public]
From: Christian König
Sent: Thursday, October 31, 2024 8:54
Am 25.10.24 um 19:41 schrieb Yunxiang Li:
Before, every time fdinfo is queried we try to lock all the BOs in the
VM and calculate memory usage from scratch. This works okay
[Public]
> From: Christian König
> Sent: Thursday, October 31, 2024 8:54
> Am 25.10.24 um 19:41 schrieb Yunxiang Li:
> > Before, every time fdinfo is queried we try to lock all the BOs in the
> > VM and calculate memory usage from scratch. This works okay if the
> > fdinfo is rarely read and the
Am 25.10.24 um 19:41 schrieb Yunxiang Li:
Before, every time fdinfo is queried we try to lock all the BOs in the
VM and calculate memory usage from scratch. This works okay if the
fdinfo is rarely read and the VMs don't have a ton of BOs. If either of
these conditions is not true, we get a massiv
Before, every time fdinfo is queried we try to lock all the BOs in the
VM and calculate memory usage from scratch. This works okay if the
fdinfo is rarely read and the VMs don't have a ton of BOs. If either of
these conditions is not true, we get a massive performance hit.
In this new revision, we
