Thrift spawns as many threads as requests, so running more than one shouldn't benefit you much I think?
I run 1 thriftserver per regionserver, co existing, and then use TSocketPool on the client side to spread load around. But generally, YES, the thrift server could be a bottleneck. The main problem with thrift and performance is you cannot control the scanner caching directly, and you cannot do bulk commits. Both of those would require some API changes, and while not impossible, just hasn't been prioritized. Personally, we use thrift for php scripts, and use the Java API for map-reduces and bulk data operations. Thus achieving the best of both worlds: cross language access from PHP and the faster Java-based API for certain scenarios. -ryan On Thu, Sep 3, 2009 at 1:08 AM, Sylvain Hellegouarch<[email protected]> wrote: >> Could I leverage that potential bottleneck by starting more than one >> Thrift server on a given machine (that would require I assume being able >> to pass a specific configuration to HBaseConfiguration in ThriftServer, >> right? > > Right scratch that last bit. I'm talking nonsense... just pass a different > port to the thrift server. Ahem. > > Anyway, I'd be interested in knowing if Thrift is known to create a major > bottleneck. > > Thanks again, > - Sylvain > -- > Sylvain Hellegouarch > http://www.defuze.org > >
