Sort Command is Slow in Memory Capped Non-Global Zones
Last updated on JANUARY 26, 2018
Applies to:Solaris Operating System - Version 10 9/10 U9 and later
Information in this document applies to any platform.
Running the "sort" command in a non-global zone configured with memory capping via rcapd takes longer than in the global zone. In some cases, it can take many seconds to complete.
A truss of the process shows a delay prior to the completion of a sysconfig() system call to obtain the number of available memory pages within the zone. The delay is proportional to the number of memory segments in use within the zone since these segments must be walked in order to obtain an accurate calculation of memory usage. Below, we see a delay of over 16 seconds between the completion of the previous system call and the completion of the sysconfig() call.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms