Bug 1041599

Summary: [RFE][swift]: profiling middleware
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/swift/+spec/profiling-middleware
Whiteboard: upstream_milestone_none upstream_status_implemented upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:58:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 18:10:46 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/profiling-middleware.

Description:

Performance tuning is a big topic. The current profiling method monitor the cluster and provide system and process level statistics information which can tell how well the system is running. But it doesn't provide more details about code level information and explain why. This proposal can give us deeper analysis into the code and tell what happened in the background and explain why. For example:
1)How often the function in specific module is called?
2)How long it take to execute these calls?
3)Where's the most time consumed?
4)Why does the response time of container PUT operation increase?
5)Where does the memory leaking happen?  how much memory consumed by specific code snippet?

Specification URL (additional information):

None