Summary: | Nfs /home client hopeless since linux kernel 6.2 | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Richard PALO <richard.palo> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | grave | CC: | nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
inxi -FAZ output on LTS
mountstats /home/richard on LTS mountstats /home/richard on mainline 6.2 nfsiostats LTS nfsiostats mainline |
Description
Richard PALO
2023-03-19 08:01:43 UTC
Created attachment 157492 [details]
mountstats /home/richard on LTS
Created attachment 157493 [details]
mountstats /home/richard on mainline 6.2
added mountstats /home/richard for both, issued as soon as possible after login and a terminal could be created. NB: these are with the option 'fsc' in the nfs mount statements in /etc/fstab I find curious over 17x the number of RPC calls in mainline 6.2 as opposed to LTS. Created attachment 157521 [details]
nfsiostats LTS
Created attachment 157522 [details]
nfsiostats mainline
rather distressing mainline nfsiostats compared with LTS
5 times total more ops/s
5x slower read ops/s and kB/s
considerable write ops/s and kB/s and kB/op reduction
Sounds you have multiple system components affected, and you said it started with kernel 6.2, I would suggest that it's a kernel issue, and recommend reporting it at https://bugzilla.kernel.org. In general, in a managed/client focused environment, I would strongly recommend either using an LTS style distro like Kubuntu, or having an internal QA process to prevent certain updates from reaching clients. Arch is a very fast-moving distro and it's expected that things will break once in a while, with Arch users being expected to be able to troubleshoot and report informed bug reports. If this doesn't describe your clients, a different distro might be a better fit. BTW, who is "we"? Can you provide some details about your use of Plasma on these machines? It sounds interesting. (In reply to Nate Graham from comment #6) > Sounds you have multiple system components affected, and you said it started > with kernel 6.2, I would suggest that it's a kernel issue, and recommend > reporting it at https://bugzilla.kernel.org. > > In general, in a managed/client focused environment, I would strongly > recommend either using an LTS style distro like Kubuntu, or having an > internal QA process to prevent certain updates from reaching clients. Arch > is a very fast-moving distro and it's expected that things will break once > in a while, with Arch users being expected to be able to troubleshoot and > report informed bug reports. If this doesn't describe your clients, a > different distro might be a better fit. > > BTW, who is "we"? Can you provide some details about your use of Plasma on > these machines? It sounds interesting. Sorry, I guess I missed your response. In general, we (our site) uses linux-lts, but with the clients we tended toward mainstream for better hw support. This was quite important when the clients were aarch64 but now that we've gone back to x86_64 with Ryzen, there is a bit less problem there. The choice of plasma on the clients was two-fold, first, certain tools like the pdf viewer okular are (in our usage) superior to the usual evince or equivalent, mainly because we send/receive lots of 'electronically signed' pdfs. Using LibreOffice for signing or verifying signatures was a PITA with pdfs. Secondly, now that we have more memory on the clients due to moving back to x86_64, the user experience is more appreciated under plasma -- once the changes with the initial exposure migrating from lxde/lxqt was overcome [naturally]. These users are administrative/finance users in an SME where NFS home simplifies considerably the system administration. I'll check with the latest 6.2 update to see if there's any change, if not I'll file an issue upstream linux as suggested. cheers |