Well,
i understood that. But the thing is...
There is the "message" or better "event" based
communication paradigm and there is the "thread" based
communication paradigm.
Is there an alternative to that both possibility ?
I at least see no one in what doug described.
Either you have one thread per pipe and since there
should be one pipe for each connection you end up in
one thread per connection.
Or you have one thread/several threads for a set of
pipes, but in this case that would be just another
disguise event based solution.
... from what i know.
wdyt ?
Johannes
-- Stefan Groschupf <[EMAIL PROTECTED]> schrieb:
> Hi Johannes,
> right, but in case you have 200 boxes and each box
> need to open 4
> different connections to the master.
> Than the master has 200 * 4 connections = 800
> threads = the limit of
> the 2.4 kernel.
> In case you open only one conenction per box you are
> also limited to
> run 800 boxes per master.
> Since map reduce is focused to have thousands of
> boxes involved this
> would be a limitation. (google has actually more
> than 150.000 :-O
> boxes I had read in a interesting book)
>
> Stefan
>
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden:
http://mail.yahoo.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
