Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146208

Summary: Watchman throttler plugin defaults are very aggressive
Product: OpenShift Container Platform Reporter: Timothy Williams <tiwillia>
Component: UnknownAssignee: Brenton Leanhardt <bleanhar>
Status: CLOSED DEFERRED QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 2.1.0CC: jokerman, lmeyer, mmccomas, nicholas_schuetz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-18 19:18:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1167895    

Description Timothy Williams 2014-09-24 18:45:36 UTC 
Description of problem:
The watchman throttler plugin's defaults are very aggressive for a default value. The defaults are:

  apply_percent: 30
  restore_percent: 70

This means that when a gear is using 30% (or more) of its allocated cpu limit for 120 seconds, it will be throttled. This is very aggressive, as the gear has not reached near its normal cgroup limit before being throttled. If a healthy gear consistently uses ~32% cpu, it will be throttled without justification. 

The defaults make sense for OpenShift online, but may not make sense for what we expect a normal OpenShift Enterprise deployment to be. 

Version-Release number of selected component (if applicable):
2.1

Additional info:
Since the throttler is barely documented, it is also confusing to customers when healthy gears are throttled. https://bugzilla.redhat.com/show_bug.cgi?id=1146147
Comment 2 Randall Theobald 2014-09-24 19:13:10 UTC 
For many OSE installers, one of the first things they will do is some sort of performance testing. When they see the throttling and have no idea what is going on, there will be some WTF moments...

I'd suggest you carefully consider what the defaults should be for OSE. One option should be that throttling is disabled completely by default, and admins can enable it if they are targeting a high-density environment with development activities (instead of pure production deployments).
Comment 3 Timothy Williams 2016-04-18 19:18:39 UTC 
This is intended behavior and has been documented.
Comment 4 Timothy Williams 2016-04-18 19:19:18 UTC 
*** Bug 1167893 has been marked as a duplicate of this bug. ***