I've got a customer running AIX 4.3.3 and Progress
8.3 (I know it's old) and they got performance
problems.
vmstat show around 70% system (sys) and 30% application (usr) time, which use to be the opposit relation.
When tracing AIX I can see that "normal" unix cmds, like mv, cp, rm etc., is taking alot of CPU cycles comparing to _progres processes.
The most used syscall (system call) is execve which is far ahead of all other syscall.
It looks like the application or Progress isself is exec'ing unix cmds and for some reason this takes time. During several measurements the rm cmd took around 1 second each time which sounds a bit to long for.
Does anyone seen a similar behaviour?
Regards Mike
karman@se.ibm.com
8.3 (I know it's old) and they got performance
problems.
vmstat show around 70% system (sys) and 30% application (usr) time, which use to be the opposit relation.
When tracing AIX I can see that "normal" unix cmds, like mv, cp, rm etc., is taking alot of CPU cycles comparing to _progres processes.
The most used syscall (system call) is execve which is far ahead of all other syscall.
It looks like the application or Progress isself is exec'ing unix cmds and for some reason this takes time. During several measurements the rm cmd took around 1 second each time which sounds a bit to long for.
Does anyone seen a similar behaviour?
Regards Mike
karman@se.ibm.com