On Sun, May 07, 2023 at 02:45:53PM +0200, Łukasz Wąsikowski wrote: > Hi, > > I'm using Linstor on 5 node Proxmox 7.x cluster. After recent upgrade I've > got some performance issues with some linstor queries. > > Upgrade: linstor-common:amd64 (1.20.2-1, 1.22.1-1), python-linstor:amd64 > (1.16.0-1, 1.18.0-1), linstor-client:amd64 (1.16.0-1, 1.18.0-1), > linstor-controller:amd64 (1.20.2-1, 1.22.1-1), linstor-satellite:amd64 > (1.20.2-1, 1.22.1-1), linstor-proxmox:amd64 (6.1.0-1, 7.0.0-1)
I'm pretty sure this isn't a LINSTOR issue but more a linstor-proxmox issue: Proxmox calls the plugins status API *a* *lot*. And in case of LINSTOR it isn't only that 1 nodes calls the controller a lot, but all the nodes query it separately. There is a "cache" in the Proxmox API and we even rolled our own that is stored persistently in the file system. With 7.0.0 we are in a situation where we can not use the cache as efficient as before, and I guess that shows. You can a) increase "statuscache", or you can downgrade to 6.1.0. 6.1.0 should be fine, the only thing that changed was improved storage information, but if you have been happy so far, please downgrade. I have an idea how we can keep the information in the cache more efficiently, but that will also require some development effort in LINSTOR itself. Regards, rck _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list drbd-user@lists.linbit.com https://lists.linbit.com/mailman/listinfo/drbd-user
