Hi guys,
Thanks a lot for the replies and sorry for the late response!
So yeah, I do agree that the setting as poor right now. Appart from so many page faults, the isn't a sensible impact in performance. Actually as zaxxon pointed out, there isn't a whole lot of I/O happening here.
As for the tuning recommendations, they seem right, in fact they are a lot more in accordance to what this white paper says:
http://www.ibm.com/developerworks/forums/servlet/JiveServlet/download/747-3
(page 14)
But to be honest I can't really touch that. I'm more of application/dev level, so I'm trying to figure out what I could tell from my pov what could be done.
For now, I can only report what I've found to be 'normal' according to the current settings, and forward the white book as a guide line.
Besides, these flags seem to have been changed already. The guys doing it had they reason and knowledge for that.
Nevertheless, I'll monitor any changes they make in the server and let you guys know as it gets sorted.
Still, I wish I could tell more precisely, i.e. 1+1=2, why I'm seeing so much page faults.
While I can see that 20% maxperm, would drive my LRU nut trying to free more space in a memory intense environment, I cant really grasp how it causes so many page faults...
A guy from the IBM forum following the same tread said that I probably wont be able to figure that out without deep knowledge of what's running. That's somewhat... unsaddling.. I mean, would that mean that to fine tune my memory manager, I have to be a specialist in everything that runs in a server plus the server itself? I'd prefer to believe in a JVM-like world, where I can monitor and test GC's statistics and figure out my settings without having to know a lot of what or how does the program does...
cheers,
f.
EDIT - removed grumpiness