在咱们的工做中,咱们使用ddagent ver。5做为收集工具,收集和报告托管服务器的性能指标,并对ddagent进行必定程度的定制。通过屡次功能迭代,发现一批在线运行时间长的托管服务器占用了太多内存。分析问题机器上进程树中每一个节点的占用状况,能够看出ddagent集合进程的内存占用仍然很高。java
咱们将学习最基本的流程控制工具,好比python
做为保证业务系统稳定运行的监控组件,存在内存泄漏,这天然是很是严重的,因此咱们开始了咱们的“故障排除之旅”。编程
有不少工具能够分析和导出Python程序的内存状态。在这里,咱们使用pyrasite,它能够附加到正在运行的Python程序,生成内存快照,并检查当前哪些对象类型占用了多少内存,并从大到小排序。json
使用命令很是简单: pyrasite-memory-viewer <PID>
,同时会生成一份快照文件: /tmp/pyrasite-<PID>-objects.json
。bootstrap
因为没法提供真实的生产数据,下面提到的全部数据都来自问题版本在测试环境中运行12小时后的采样。数组
在pyrasite提供的Cui视图中,咱们能够清楚地看到字典类型的对象实例占用的内存最多,达到3.4mb,有6621个实例:安全
while 循环服务器
While循环也是一种常见的循环方式。这种循环一般以循环体类或条件方式结束。它不可能无限期地进行下去。app
对于泄漏状况,咱们有如下事实和猜想:python2.7
[ [ [".../embedded/lib/python2.7/threading.py",774,"__bootstrap","self.__bootstrap_inner()"], [".../embedded/lib/python2.7/threading.py",801,"__bootstrap_inner","self.run()"], [".../modules/monitor/bot/schedule.py",51,"run","task.run()"], [".../modules/monitor/bot/task.py",50,"run","super(RepeatTask, self).run()"], [".../modules/monitor/bot/task.py",18,"run","self.check()"], [".../modules/monitor/checks/collector.py",223,"wrapper","_check.run()"], [".../modules/monitor/checks/__init__.py",630,"run","self._roll_up_instance_metadata()"], [".../modules/monitor/checks/__init__.py",498,"_roll_up_instance_metadata","dict((k, v) for (k, v) in self._instance_metadata))"], [".../modules/monitor/tracer.py",33,"__init__","self.trace_info = traceback.extract_stack()"] ], [ [".../embedded/lib/python2.7/threading.py",774,"__bootstrap","self.__bootstrap_inner()"], [".../embedded/lib/python2.7/threading.py",801,"__bootstrap_inner","self.run()"], [".../modules/monitor/bot/schedule.py",51,"run","task.run()"], [".../modules/monitor/bot/task.py",50,"run","super(RepeatTask, self).run()"], [".../modules/monitor/bot/task.py",18,"run","self.check()"], [".../modules/monitor/checks/collector.py",223,"wrapper","_check.run()"], [".../modules/monitor/checks/__init__.py",630,"run","self._roll_up_instance_metadata()"], [".../modules/monitor/checks/__init__.py",498,"_roll_up_instance_metadata","dict((k, v) for (k, v) in self._instance_metadata))"], [".../modules/monitor/tracer.py",33,"__init__","self.trace_info = traceback.extract_stack()"] ], [ [".../embedded/lib/python2.7/threading.py",774,"__bootstrap","self.__bootstrap_inner()"], [".../embedded/lib/python2.7/threading.py",801,"__bootstrap_inner","self.run()"], [".../modules/monitor/bot/schedule.py",51,"run","task.run()"], [".../modules/monitor/bot/task.py",50,"run","super(RepeatTask, self).run()"], [".../modules/monitor/bot/task.py",18,"run","self.check()"], [".../modules/monitor/checks/collector.py",223,"wrapper","_check.run()"], [".../modules/monitor/checks/__init__.py",630,"run","self._roll_up_instance_metadata()"], [".../modules/monitor/checks/__init__.py",498,"_roll_up_instance_metadata","dict((k, v) for (k, v) in self._instance_metadata))"], [".../modules/monitor/tracer.py",33,"__init__","self.trace_info = traceback.extract_stack()"] ], ...
咱们不提“作好设计审查和规范审查”、“增强试验阶段质量检验工做”等“老生常谈”,也值得咱们反思。
要完全防止和控制内存泄漏几乎是不可能的,像rust这样的安全编程语言也不能保证程序不会泄漏内存。
许多引起内存不安全的行为,如数组访问越界、访问释放后的内存等,均可以经过制定更严格的编程模型(如rust提出的全部权+生命周期规则)甚至数据竞争问题来避免。
然而,触发内存泄漏的行为,如竞争条件,须要开发人员将开发组件和业务规则结合起来。设想一个须要手动触发刷新的数据队列。结果,咱们在推送数据时忘记调用它。这种内存泄漏没法经过任何常规检查规则来识别。
关键字函数是为了更形象地说明传入参数的位置和具体用法。若是一个函数有四个或五个参数,并且一次传入的参数太多,那么很难让人眼花缭乱。若是key=value用于传入。
经过本节的学习,咱们了解了经过if else在不一样条件下控制代码流和执行不一样代码。for/while和如何定义函数有两种不一样的循环方法,包括函数的返回值和参数传递方法、position参数传递和向函数传递参数时的key=value参数传递。