Hi Erich,
in our case the "client failing to respond to cache pressure" situation
is/was often caused by users how have vscode connecting via ssh to our
HPC head node. vscode makes heavy use of file watchers and we have seen
users with > 400k watchers. All these watched files must be held in t
Hi Dietmar,
We do in fact have a bunch of users running vscode on our HPC head node
as well (in addition to a few of our general purpose interactive compute
servers). I'll suggest they make the mods you referenced! Thanks for
the tip.
cheers,
erich
On 4/24/24 12:58 PM, Dietmar Rieder wrot
Hi Erich,
hope it helps. Let us know.
Dietmar
Am 26. April 2024 15:52:06 MESZ schrieb Erich Weiler :
>Hi Dietmar,
>
>We do in fact have a bunch of users running vscode on our HPC head node as
>well (in addition to a few of our general purpose interactive compute
>servers). I'll suggest they
Actually should I be excluding my whole cephfs filesystem? Like, if I
mount it as /cephfs, should my stanza looks something like:
{
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/*/**": true,
"**/.cache/**": tru
there might be situations/dicrectories for which it makes a lot of sense
that they are watched for changes and vscode is informed about these. So
excluding the entire cephfs might not always be a good idea. But I guess
you need to find out.
Dietmar
On 4/27/24 16:38, Erich Weiler wrote:
Actua
