[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: how long should the manager maintain the connection with his device?



Hi Wang,

 

Our product achieves 6000 connections with both stock Solaris-9 and RedHat-ES based systems. ÂAs for the hardware, our sizing guides suggest customers have about 4 gigs of memory, but the majority of this memory is not for TCP. ÂHonestly, we did this without much consideration for if it could be done â in fact, we have another product that does over 10,000 connections on a single machineâ Maybe it is because we are using the C programming language with a single select()-driven thread?

 

But the point I was trying to make, in answering your original question, is that managers do like to hold persistent connections â I say âlikeâ as it is easy to implement without great impact to either the endpoints or the network in-between.

 

Kent

 


From: y030737@njupt.edu.cn [mailto:y030737@njupt.edu.cn]
Sent: Wednesday, July 06, 2005 6:43 PM
To: netconf; Kent Watsen
Subject: Re: how long should the manager maintain the connection with his device?

 

Dear Kent Watsenï

  thanks for your reply.

   

      but I really can't image a single machine has the capability that maintains  persistence connections

with *6000*  device. 

 So  could you please tell me the machine's type, and how do you get the number "6000" ??

ãã

 

======== 2005-07-07 06:41:56  Kent Watsen saidï =====

 

 

The duration of the connection is closely related to how often the non-initiating side needs to flush its buffers (i.e. event notifications).  We find that persistent connections work fine for up to 6000 devices - this is the practical connection limit for a single machine.  For more than 6000 devices, either a server-cluster or a periodic-poll architecture needs to be considered - the choice pending on the interaction requirements of your system

 

When NetConf pursues event notifications, in addition to following the publish/subscribe messaging pattern it would be good to also consider the durable-subscriber and priority-queuing patterns for NMSs wishing to have non-persistent connections

 

Kent

 

 

-----Original Message-----

From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of y030737@njupt.edu.cn

Sent: Tuesday, July 05, 2005 8:21 PM

To: netconf

Subject: how long should the manager maintain the connection with his device?

 

hi all:

 

   I have read the netconf-pro06 and "scalability of netconf" topic on the list, I saw 

Juergen Schoenwaelder said he find that holding 300 TCP connections is not a hard thing.

 

   but I want to know in the real world , does the manager just hold the connection when there are still some config operation need to be performed and the connection will be kill as soon as these operations completed?  Or it will hold the connection with his "agent" all the time until some accident happens? 

 

 

thanks for coming in!

 

Best Regards

 

---------------------------------------------------

Wang Han

 

y030737@njupt.edu.cn

Research Center of Network Technology

Nanjing University of Posts and Telecommunications

---ââââââââââââââââââââââââââ

 

 

 

ærzuçzæçîåçzçæzäwrzÐçç

 

 

Regards

 

Wang Han

------------------------------------------------------------

Wang Han

 

y030737@njupt.edu.cn

Research Center of Network Technology
Nanjing University of Posts and Telecommunications
ââââââââââââââââââââââââââ