Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQTT Server is taking more heap space, if we connected client with ssl enabled. By taking the heap dump, byte[] is taking 4 times more heap compare to ssl false. Is there anything we need to? I have tried this for 1L connections. #122

Open
SivaSamrajS opened this issue Mar 20, 2019 · 1 comment

Comments

@SivaSamrajS
Copy link

  SSL FALSE False instance Count SSL TRUE True instance Count
int[] 213 MB   748 MB  
byte[] 21 MB 127764 3.45 GB 8965812
object[] 114 MB   203 MB  
sun.security.ssl 20 KB   106 MB  
com.sun.crypto.provider 143 B   127 MB  
io.netty.channel 136 MB   170 MB  
@SivaSamrajS SivaSamrajS changed the title MQTT Server is taking more heap space, if we are connected with ssl enabled. By taking the heap dump, byte[] is taking 4 times more heap compare to ssl false. Is there anything we need to? I have tried this for 1L connections. MQTT Server is taking more heap space, if we connected client with ssl enabled. By taking the heap dump, byte[] is taking 4 times more heap compare to ssl false. Is there anything we need to? I have tried this for 1L connections. Mar 20, 2019
@leeflying315
Copy link

have you tried to use boring ssl ? or open ssl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants