Surging.Core.CPlatform.Runtime.Client.Implementation.RemoteInvokeService 在创建和使用transportClient 之后没有释放 transportClient ，是否会造成内存泄漏呢

fanliang11 / surging

Surging is a micro-service engine that provides a lightweight, high-performance, modular RPC request pipeline. support Event-based Asynchronous Pattern and reactive programming ,The service engine supports http, TCP, WS,Grpc, Thrift,Mqtt, UDP, and DNS protocols. It uses ZooKeeper and Consul as a registry, and integrates it. Hash, random, polling, Fair Polling as a load balancing algorithm, built-in service governance to ensure reliable RPC communication, the engine contains Diagnostic, link tracking for protocol and middleware calls, and integration SkyWalking Distributed APM

MIT License

3.24k stars 923 forks source link

Surging.Core.CPlatform.Runtime.Client.Implementation.RemoteInvokeService 在创建和使用transportClient 之后没有释放 transportClient ，是否会造成内存泄漏呢 #396

Closed karqical2016 closed 4 years ago

karqical2016 commented 4 years ago

Surging.Core.CPlatform.Runtime.Client.Implementation.RemoteInvokeService 在创建和使用transportClient 之后没有释放 transportClient ，是会造成内存泄漏

fanliang11 commented 4 years ago

surging 使用的是RPC长连接，为什么要关闭？一个连接占用内存也就8k,一万台服务连接也就80mb左右，这点内存难道不能接受吗？

fanliang11 commented 4 years ago

https://github.com/Azure/DotNetty/issues/344 这是dotnetty的全局缓冲池默认初始化占用16MB，和transportClient无关，请自己学习或者购买服务，谢谢，社区版本只接受PR和BUG 提问

karqical2016 commented 4 years ago

购买服务怎么个价格范围，具体详情

fanliang11 commented 4 years ago

童叟无欺价企业版28000，不还价。