I just tested it out and setting NoDelay on the socket brought the rate up from 30msg/sec up to ~12k msg/sec which is fine for me for now.
What now? It looks like the guy that fixed the issue reported by Jonathan says the solution is to used a frame transport? It still looks like this is an issue with whatever the default transport is, TServerSocket I guess? Chris On Mon, Feb 7, 2011 at 3:16 PM, Diego Jancic <[email protected]> wrote: > Did you check the patch suggested by Jonathan? ( > https://issues.apache.org/jira/browse/THRIFT-904) > > It says it was resolved on 27/Jan/11 > > > On Mon, Feb 7, 2011 at 16:42, Chris Morgan <[email protected]> wrote: > >> I looked at that email thread but I didn't see any patch mentioned >> there.I also tested using the latest version of thrift from svn and >> I'm seeing the same results. >> >> I'm surprised no one has looked into this yet, guess not many people >> are interested in thrift server on mono.... >> >> Chris >> >> >> On Sat, Feb 5, 2011 at 12:19 AM, Diego Jancic <[email protected]> wrote: >> > Hi, >> > I found the same issue a long time ago (1.5 years ago: >> > >> http://www.mail-archive.com/[email protected]/msg00628.html >> ) >> > I have not tested the patch. >> > >> > Let me know if the solution works. >> > >> > On Fri, Feb 4, 2011 at 22:42, Chris Morgan <[email protected]> wrote: >> > >> >> Hello. >> >> >> >> I was running some tests to evaluate using mono to run a c# thrift >> >> server. I created a simple application that passes blobs to the server >> >> and gets a result code back. I'm running on Kubuntu Mavrick (10.10) >> >> here >> >> >> >> From testing I see: >> >> >> >> cpp client -> c# server (mono 2.6) ~30 messages/sec >> >> cpp client -> c# server (mono 2.11) ~30 messages/sec >> >> cpp client -> cpp server ~30k messages/sec >> >> >> >> The rates are the same whether or not the blob is 50 bytes or 5000 >> bytes. >> >> >> >> For my particular use 30 messages a second is a huge bottleneck. Has >> >> anyone else seen this kind of behavior? Anyone know how to fix it? >> >> >> >> Chris >> >> >> > >> >
