On Tue, Nov 3, 2020 at 3:25 PM Jim Elliott <jlelliot...@gmail.com> wrote:
> Gregory, > > Yes, thrashing. :-) > > I like my name better and it even fits better :) I will keep an eye on page faults tomorrow but we are not overcommitting memory at all. Unless something inside of db2 is cooking but in linux there is no swapping and in z/vm no paging whatsoever. DB2 grabs about 95% of the memory and it all goes into "shmem" and uses that for it's buffers and stuff. It's not like db2 has its own internal paging? Even if it did, I am sure DBAs would scream by now. Although the ~20% cpu time spent in kernel mode is something I've been questioning (rest of it goes straight into user time) . But I have no clue if it is a lot for this type of workload or not at all. I've been blaming a massive number of filesystems/logical volumes (152) and huge number of threads processes and FD's. How do you best determine that there is no some other thrashing? thanks! Gregory > Jim Elliott > Senior IT Consultant - GlassHouse Systems Inc. > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
