Related to issue #110
Added ProtocolLoadTest project to test performance of Thrift and HTTP…
Note this includes an ugly hack in ElasticClient.GetNodeInfo (as a workaround for a bug in the Thrift connection), so I guess you don't want to merge it into the master branch :)
@cocowalla i also had problems with GetNodeInfo but adhering to the chart found at
and upgrading my 19.8 to 19.9 fixed any connection issues.
I'm now seeing identical body's in the thrift index but the http index has nice random body's on the messages. Investigating the cause of this now.
I rewrote the ThriftConnection to use its own pooling (similar to how the default connection does it) and the tests to use the async overloads instead of wrapping the sync calls in tasks manually.
I'm seeing really impressive speedups using thrift!
HTTP: 12123 docs/s
Thrift: 17575 docs/s
Those are documents per second and on first inspection everything seems to be in working order.
Thank you @cocowalla for bringing thrift back in to the picture and thank you @medcl for porting your thrift connection over to NEST 👍 👍
and added: https://www.nuget.org/packages/Nest.Connection.Thrift/0.9.9.0