One of the reasons why you may not have run into these issues in your non-Production environments is due to the volume of users/activity. It's not uncommon to be unable to simulate a full Production workload in these other environments, so you wouldn't have pushed the configuration limits. It's not uncommon to see a Production server with higher configuration settings.
If any of the 'number of %' parameters are showing Pct_act at/near 100% then these parameters should be increased (eg, 'number of open indexes').
If any of the 'number of %' or 'procedure cache size' parameters are showing Reuse_cnt > 0 then these parameters will also likely benefit from an increase in their configured size (eg, 'procedure cache size') if they haven't already been bumped up (see NOTE #4 - below).
NOTES:
1 - Pct_act is dynamic and represents the current situation
2 - Max_Used shows the max used value since ASE was booted (ie, reset to 0 at ASE bootup)
3 - Reuse_cnt is a cumulative counter (reset to 0 at ASE bootup)
4 - changing a parameter (eg, any of the 'number of %' parameters') will automatically cause Num_free/Num_active to change, too; but the Max_Used and Reuse_cnt readings will not be reset; net result is that after making a config change you want to run sp_monitorconfig, save the report, then compare future sp_monitorconfig reports for any further changes/increases in Max_Used and/or Reuse_cnt to determine if you need to increase the parameters again
EXCEPTIONS:
- you can ignore 'max memory' with Pct_act = 100%; this setting should always be at/near 100%
- 'permission cache entries' is a hit-or-miss setting; some value of Reuse_cnt is likely unavoidable; if you see really large Reuse_cnt values (eg, millions+) then you may want to increase this parameter, too
SUGGESTIONS:
- while 'number of open partitions' is showing Reuse_cnt = 44,206, this appears to be leftover from prior to your increase in this parameter ('number of open partitions' = 80,000, Max_Used = 60,000 => no reuse since increasing the setting to 80,000); no need to change 'number of open partitions' at this point in time (if you see Max_Used approach 80,000 and/or Reuse_cnt go above 44,206 then you'll want to increase the value)
- 'number of open indexes' = 60,000, Pct_act = 100% and Max_Used = 60,000 => definitely want to increase this value; Reuse_cnt = 0 means you've been lucky so far, but I'd want to play it safe and increase this parameter to 100K-120K
- 'permissions cache entries' Reuse_cnt = 6,823; this is pretty low so I'd probably not worry about this setting for now; on the other hand, it won't require much memory if you want to double the current setting to see what happens with future usage stats
- 'procedure cache size' *current* Pct_act = 99.12% (too high), Max_Used = 262,144 (same as current configured value => too high), and Reuse_cnt = 54,949 (anything > 0 for 'procedure cache size' is definitely too high); I'd probably start by bumping this parameter up to 500K, make note of the Reuse_cnt value at that time, then pay careful attention to future sp_monitorconfig reports and be ready to increase again should Reuse_cnt continue to climb
- obviously (?) increasing any of these configuration parameters will require memory, so if you attempt to increase these values and you get a message that there is not enough memory, then you'll need to consider either a) increasing 'max memory' (assuming there's some free memory on the machine) or b) reduce some other memory-using parameter (eg, a data cache/pool) and reboot the dataserver