- Peer/Orderer memory usage
Re: Peer/Orderer memory usage
toggle quoted messageShow quoted text
There's a known goroutine leakage in 1.4.4. You may need to apply this patchset.
During our performance tests, we noticed that, both peers’ and orderers’ memory usage is increasing under load and
they do not release the claimed memory when the load is removed.
Is this expected? Anything we can do about it on the configuration side?
Peers: Up to 15G -> This is especially very high
Orderers: Up to 4G
Fabric version: 1.4.4
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by
you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of
internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement
Join firstname.lastname@example.org to automatically receive all group messages.