Fri Mar 23 11:59:14 CET 2007
On 3/23/07, Raimo Niskanen <raimo+erlang-questions@REDACTED> wrote:
> It does not seem likely you have "a process called prim_inet:send/2".
> It is also not likely it was spawned as prim_inet:send/2.
> The most likely option is that you have a process stuck in
> prim_inet:send/2 where it has given a command to the inet driver
> and is waiting for the response.
>> You are exactly right. I think the exact function is
So, is this process the only one sending replies to your clients?
> And why does it get so many messages from other Erlang processes,
> and is there no flow control on those messages.
> The normal way to design a server handling many clients is to
> have one listening process and when accepting connections
> branch them off to separate processes for each TPC connection.
> Then the clients can be handled in parallel within the server.
> Try such a design and see if it helps.
>>In our case too every client will communicate to the server through
seperate TCP/IP communication.[Surindar]
On Thu, Mar 22, 2007 at 08:17:39PM +0530, Surindar Sivanesan wrote:
> > Dear all,
> > We have developed a server using erlang in Windows server 2003. As many
> > 200 client would be simultaneously connected to this server through
> > connection. When I view the process manager table in the server, an
> > internal process called prim_inet:send/2 is always having around 400
> > messages in queue. Why this process is always having messages in queue?
> > Whether it will affect the performance of the system in any way? If so,
> > there any way to sort out the problem?
> > Please give your inputs...!
> > --
> > with regards,
> > S.Surindar
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://www.erlang.org/mailman/listinfo/erlang-questions
> / Raimo Niskanen, Erlang/OTP, Ericsson AB
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions