Sorry, got threads mixed up, but yes the solution is the same.
On Mon, Sep 20, 2010 at 12:40 PM, Michael Greene
wrote:
> That... is this thread. I'm glad the solution works for you Morten.
>
>
> On Mon, Sep 20, 2010 at 12:33 PM, Michal Augustýn <
> augustyn.mic...@gmail
he.org/msg06024.html>Augi
>
> 2010/9/20 Morten Wegelbye Nissen
>
> On 19-09-2010 23:50, Michael Greene wrote:
>>
>>> Trunk (and 0.7) use Thrift's framed transport, so you should wrap your
>>> TSocket in a TFramedTransport. On 0.6 and earlier you sho
Trunk (and 0.7) use Thrift's framed transport, so you should wrap your TSocket
in a TFramedTransport. On 0.6 and earlier you should have been wrapping with a
TBufferedTransport for better performance but the framed transport is
inherently buffered.
On Sep 19, 2010, at 4:31 PM, Morten Wegelbye
This is the correct cause. Reproducing your test gives 38-45ms in each of
10 runs. If you run a profiler against it, you can see that the time is
entirely spent blocking on receive in TStreamTransport.Read.
Your test can be modified with the following line:
coreTransport.TcpClient.NoDelay = true
On Wed, Apr 14, 2010 at 11:01 PM, Ken Sandney wrote:
> a fuse based FS maybe better I guess
This has been done, for better or worse, by jdarcy of http://pl.atyp.us/:
http://github.com/jdarcy/CassFS
