Thanks for the information, Mark. This is not a criticism of Thrift,
but sometimes having more threads than the number of cores is
desirable when you have a thread pool with worker threads doing
network/disk I/O. I have programmed with both a message passing model
and a worker thread model, and in my opinion, the latter results in
more readable code and is easier to program with, especially with
languages such as C++ that require explicit memory management. I
suppose it is possible to keep most of code in a worker thread model
and just use a queue of requests at the lowest level where I need to
make Thrift RPC calls. I was hoping that Thrift would do this for me
out of the box. :-D
Cheers,
Akshat
If that is what your doing, then you might want to create a pool of
thrift connections your threads can check out, work with, and then check
back in. In this case, its often helpful to have a super lightweight
service method that can be used to test the connection before giving it
to the thread, so you can reconnect if necessary.
-Matt
