Closed yyx511 closed 9 years ago
这并不能证明内存泄露了吧。。 cached的内存也在增加
2015-01-07 11:35 GMT+08:00 yyx511 notifications@github.com:
1、环境说明: 服务器配置: CPU:16核Intel(R) Xeon(R) CPU E5620@ 2.40GHz 内存:20G 硬盘:900G 网卡:(eth5)Intel Corporation I350 Gigabit Network Connection (rev 01) 8队列千兆(队列绑定到后8个CPU核) 系统:CentOS release 6.4 (Final) 内核版本: [image: image] https://cloud.githubusercontent.com/assets/8213049/5640481/e5c12e2a-9660-11e4-9ca5-4787bd582a5c.png tengine版本: [image: image] https://cloud.githubusercontent.com/assets/8213049/5640487/f05af41a-9660-11e4-97fa-227601200528.png 2、测试前,加载fastsocket.ko(默认参数),使用libfsocket.so启动tengine [image: image] https://cloud.githubusercontent.com/assets/8213049/5640499/0e7ec8ea-9661-11e4-8206-239e0e968746.png [image: image] https://cloud.githubusercontent.com/assets/8213049/5640501/13b22a96-9661-11e4-8aa8-c4707bbf6f9f.png 3、Client用wrk [image: image] https://cloud.githubusercontent.com/assets/8213049/5640502/191b23c0-9661-11e4-9632-0df6d4ae0623.png 4、测试完成后,内存情况 [image: image] https://cloud.githubusercontent.com/assets/8213049/5640505/1e7470c4-9661-11e4-9dc6-ade7d91d407e.png 几分钟后,内存情况 [image: image] https://cloud.githubusercontent.com/assets/8213049/5640507/24c38686-9661-11e4-8bc3-4d64ac6f9865.png 又几分钟后,内存情况 [image: image] https://cloud.githubusercontent.com/assets/8213049/5640510/2ad0ecf8-9661-11e4-8198-c28cf10e4878.png 同样用fastos, 不加载fastsocket.ko,不使用libfsocket.so启动tengine,则不存在泄漏。
— Reply to this email directly or view it on GitHub https://github.com/fastos/fastsocket/issues/28.
1、环境说明: 服务器配置: CPU:16核Intel(R) Xeon(R) CPU E5620@ 2.40GHz 内存:20G 硬盘:900G 网卡:(eth5)Intel Corporation I350 Gigabit Network Connection (rev 01) 8队列千兆(队列绑定到后8个CPU核) 系统:CentOS release 6.4 (Final) 内核版本: 有执行nic.sh脚本 tengine版本: 2、测试前,加载fastsocket.ko(默认参数),使用libfsocket.so启动tengine 3、Client用wrk 4、测试完成后,内存情况 几分钟后,内存情况 又几分钟后,内存情况 同样,用fastos, 不加载fastsocket.ko,不使用libfsocket.so启动tengine,则不存在泄漏。 用fastsocket,tengine作proxy不存在泄漏。
不知是否遇到此问题,还是我本人的测试有问题,求指导。