The first test kernel (5.15.0-67-generic #74+test20230307b2h2cbb6062f8eb-Ubuntu) merely reverts file access cache-related commits.
However, the second test kernel (5.15.0-67-generic #74+test20230308b0h1a13a615ee32-Ubuntu) truly identifies and resolves the problem.
The file access cache, which belongs to the user, will be cleared once the user logs out and logs in again.
After that, all behavior will be the same as usual.
We would appreciate it if you could use the second test kernel for testing and confirm that it has resolved the performance issue.
The first test kernel (5.15.0-67-generic #74+test2023030 7b2h2cbb6062f8e b-Ubuntu) merely reverts file access cache-related commits. 8b0h1a13a615ee3 2-Ubuntu) truly identifies and resolves the problem.
However, the second test kernel (5.15.0-67-generic #74+test2023030
The file access cache, which belongs to the user, will be cleared once the user logs out and logs in again.
After that, all behavior will be the same as usual.
We would appreciate it if you could use the second test kernel for testing and confirm that it has resolved the performance issue.