Re: Improving unfsd scalability

[Olaf Kirch <okir@suse.de>]

On Thu, Nov 30, 2006 at 07:27:15PM +0100, Peter Astrand wrote:
> > I just wish people would leave this old code to Rot In Peace :)
> 
> Yes, the old ONC RPC code is far from optimal. But, what do you suggest 

Oh, I'm sorry. I was referring to unfsd.

> instead? TI-RPC? It has thread support, but it's also much more 
> complicated. The implementation is not as tested and the libtirpc 
> implementation is not based on the latest Sun release. And, libtirpc has 
> not been ported to Windows yet, and the thread stuff makes porting 
> somewhat difficult. 

I'm not a huge fan of TIRPC either.

> Btw, I'm also not convinced that threading is the best solution. I tend to 
> like multi-process or select-based solutions better.

I agree.  It makes for trickier code though.

The premise of the "java way" of writing network services (one thread
per connection) is you trade complexity for computing resources. If
you create complex applications, you need expensive programmers and
QA. If you solve a problem by throwing more threads at it, the customer
will need more expensive hardware - which is too bad, but at least
it doesn't show up on your R&D budget :)

Olaf
-- 
Walks like a duck. Quacks like a duck. Must be a chicken.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs