2016-05-04, 10:21 AM
This happens because we don't have a good documentation 
I hope to have time after v0.8.0 release.
You are right, keepalive variations doesn't make change, it doesn't work or we are misunderstanding its purpose. AFAIK you can define timeout when make a normal connection but not in publish.single function.
Anyway, after doing some test, my number of sockets is high but stable, they born and die, and it seems that doesn't affect performance. Many of open sockets belong to kplex and internal OP jobs (sensors, calculations...). I need to test with a really high number of mqtt topics and publications to see if the system endures or we have to change strategy.
Thanks Davide, you are being really helpful debugging OP
I hope to have time after v0.8.0 release.You are right, keepalive variations doesn't make change, it doesn't work or we are misunderstanding its purpose. AFAIK you can define timeout when make a normal connection but not in publish.single function.
Anyway, after doing some test, my number of sockets is high but stable, they born and die, and it seems that doesn't affect performance. Many of open sockets belong to kplex and internal OP jobs (sensors, calculations...). I need to test with a really high number of mqtt topics and publications to see if the system endures or we have to change strategy.
Thanks Davide, you are being really helpful debugging OP