Thread: [OpenSIPStack] Call Capacity Stats
Brought to you by:
joegenbaclor
Menu
▾
▴
opensipstack-devel
|
From: Chris V. <chr...@gm...> - 2008-01-09 03:05:29
|
Does anyone have additional information or a baseline for call stats(calls/sec, concurrent calls) and the associated hardware used to generate those baseline numbers? Currently we are seeing 60-80 concurrent calls with media with V1.1.5 in B2BUA mode, but have not measured calls/sec. Would using a 64-bit OSBC instance and 64 bit Fedora Core OS increase these stats? |
|
From: <jo...@op...> - 2008-01-09 05:22:08
|
Chris Veazey wrote: > Does anyone have additional information or a baseline for call stats(calls/sec, concurrent calls) and the associated hardware used to generate those baseline numbers? > > > Currently we are seeing 60-80 concurrent calls with media with V1.1.5 in B2BUA mode, but have not measured calls/sec. > If your basis would be CPU consumption, i would say 15-20 CPS is the throughput of OpenSBC in terms of signaling. Anything greater than this would result to an increase in Queue size. Media proxy calls are expensive because of the need for two separate rtp sessions, each having their own threads and would contribute on CPU load. This would have a direct impact on the CPS, thus expect lower rates when proxying media. > > Would using a 64-bit OSBC instance and 64 bit Fedora Core OS increase these stats? > > All our servers are 64 bit so i don't have any point of comparison. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > |
|
From: Chris V. <chr...@gm...> - 2008-01-10 17:32:11
|
So are the concurrent calls stats we are seeing correct? Is there anyway we can get past 60-80 concurrent calls? |
|
From: ehernaez <ope...@op...> - 2008-01-11 04:39:13
|
What are you CPS stats? Concurrent calls are only part of the picture. Is the application busy processing failed call sessions because only a small fraction actually connect? |
|
From: Chris V. <chr...@gm...> - 2008-01-11 21:31:23
|
We are ramping from 1-10 call/sec in 1 call increments and 2 minute hold times. We see the OSBC processes die when we hit about ~60 concurrent calls. The time it takes for the OSBC processes to die depend on the number of call/sec. So 1call/sec we die at about 60-80 seconds. At 10 calls/sec, we die in 6-8 seconds. |
|
From: <jo...@op...> - 2008-01-12 02:42:10
|
I don't think you are hitting a call capacity limit but an OS limit. OpenSBC should not die in this kind of very forgiving test scenario in 60 concurrent call. For example, we have servers that accepts 300-400 simultaneous connections and the only side effect of this is very high CPU usage not crashes. 10 CPS is well within OSBC capabilities. I am suspecting that you still have a misconfiguration somewhere in terms of the number of per process file handles your system accepts. ulimit -n is not always guarantee that actual os limits are adjusted due to misconfigurations somewhere. Lastly, there were recent bug fixes that indeed caused crashes in OpenSBC commited within the last five days. You might want to checkout the latest. Chris Veazey wrote: > We are ramping from 1-10 call/sec in 1 call increments and 2 minute hold times. We see the OSBC processes die when we hit about ~60 concurrent calls. The time it takes for the OSBC processes to die depend on the number of call/sec. So 1call/sec we die at about 60-80 seconds. At 10 calls/sec, we die in 6-8 seconds. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > |
|
From: Chris V. <chr...@gm...> - 2008-01-12 18:52:35
|
Is that 300-400 with or without media anchoring? Also are you referencing OS level thread handlers or the OSBC configuration parameters like Transaction Thread Count and Session Thread Count? |
|
From: Joegen E. B. <joe...@gm...> - 2008-01-13 01:40:45
|
Chris Veazey wrote: > Is that 300-400 with or without media anchoring? > > Our configuration only proxy media when needed. If the call came from a NATed device or terminates to one, then we do media anchoring on those calls. Ball park estimate, I'd say 60-40 where 60% of those calls are media anchored. > Also are you referencing OS level thread handlers or the OSBC configuration parameters like Transaction Thread Count and Session Thread Count? > > > No. I am referring to the hard limit set by the operating system for the number of file handles per process. Transaction Thread Count and Session Thread Count are finite pools of threads which should not grow parallel to traffic. You would normally do not want to manually increase the default value for these parameters unless you have reason to do so. > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: Whit T. <de...@wh...> - 2008-04-04 13:28:26
|
Joergen, Do you have the hardware/OS specs of the server you describe that is running 300-400 simultaneous connections on OSBC? Whit -----Original Message----- From: ope...@li... [mailto:ope...@li...] On Behalf Of Joegen E. Baclor Sent: Saturday, January 12, 2008 9:41 PM To: ope...@op...; ope...@li... Subject: Re: [OpenSIPStack] Call Capacity Stats Chris Veazey wrote: > Is that 300-400 with or without media anchoring? > > Our configuration only proxy media when needed. If the call came from a NATed device or terminates to one, then we do media anchoring on those calls. Ball park estimate, I'd say 60-40 where 60% of those calls are media anchored. > Also are you referencing OS level thread handlers or the OSBC configuration parameters like Transaction Thread Count and Session Thread Count? > > > No. I am referring to the hard limit set by the operating system for the number of file handles per process. Transaction Thread Count and Session Thread Count are finite pools of threads which should not grow parallel to traffic. You would normally do not want to manually increase the default value for these parameters unless you have reason to do so. > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ opensipstack-devel mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: Joegen E. B. <joe...@gm...> - 2008-04-04 17:54:49
|
It was Chris who described the 300-400 traffic. In my personal experience, a dual core Opteron can handle 30 CPS at 400 active connections without critical increase in event queue size. Whit Thiele wrote: > Joergen, > > Do you have the hardware/OS specs of the server you describe that is running > 300-400 simultaneous connections on OSBC? > > Whit > > > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] On Behalf Of > Joegen E. Baclor > Sent: Saturday, January 12, 2008 9:41 PM > To: ope...@op...; > ope...@li... > Subject: Re: [OpenSIPStack] Call Capacity Stats > > Chris Veazey wrote: > >> Is that 300-400 with or without media anchoring? >> >> >> > Our configuration only proxy media when needed. If the call came from a > NATed device or terminates to one, then we do media anchoring on those > calls. Ball park estimate, I'd say 60-40 where 60% of those calls are > media anchored. > > > >> Also are you referencing OS level thread handlers or the OSBC >> > configuration parameters like Transaction Thread Count and Session Thread > Count? > >> >> > > No. I am referring to the hard limit set by the operating system for > the number of file handles per process. Transaction Thread Count and > Session Thread Count are finite pools of threads which should not grow > parallel to traffic. You would normally do not want to manually > increase the default value for these parameters unless you have reason > to do so. > > >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> >> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > >> _______________________________________________ >> opensipstack-devel mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >> >> >> >> > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: Chris V. <chr...@gm...> - 2008-01-14 03:11:28
|
Do you have some explicit OS level changes that can be applied to increase/tweak the file handlers? |
|
From: Chris V. <chr...@gm...> - 2008-01-14 13:35:32
|
Are you referring to tweaks like sysctl -a --> fs.file-max? |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X