Hi,
the best way to debug something like that is to start with top. start top
then press 1 and check if any of the cores has almost 0% idle while others
have plenty of CPU left. if that is the case you have one very hot thread.
to further isolate it you can press 1 again to collapse the cores,
At a guess with no data if the application is opening more files than
can fit in the maxFilesToCache (MFTC) objects GPFS will expand the MFTC to
support the open files, but it will also scan to try and free any unused
objects. If you can identify the user job that is causing this
Hello Scalers,
First, let me say Happy Thanksgiving to those of us in the US and to those
beyond, well, it's a still happy day seeing we're still above ground!
Now, what I have to discuss isn't anything extreme so don't skip the turkey for
this, but lately, on a few of our compute GPFS
