2008
DOI: 10.1007/978-3-540-89054-6_7
|View full text |Cite
|
Sign up to set email alerts
|

One Server Per City: Using TCP for Very Large SIP Servers

Abstract: Abstract. The transport protocol for SIP can be chosen based on the requirements of services and network conditions. How does the choice of TCP affect the scalability and performance compared to UDP? We experimentally analyze the impact of using TCP as a transport protocol for a SIP server. We first investigate scalability of a TCP echo server, then compare performance of a SIP registrar server for two TCP connection lifetimes: transaction and persistent. Our results show that a Linux machine can establish 400… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
7
2

Relationship

1
8

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 8 publications
0
9
0
Order By: Relevance
“…They also conclude that authentication considerably affects the performance of the proxy. Ono et al [18] analyze how the use of TCP affects the performance and scalability of a proxy proposing several configuration changes to improve performance. Cortes et al [8] evaluate the parsing, string processing, memory allocation, thread overhead and overall capacity of a proxy.…”
Section: Related Workmentioning
confidence: 99%
“…They also conclude that authentication considerably affects the performance of the proxy. Ono et al [18] analyze how the use of TCP affects the performance and scalability of a proxy proposing several configuration changes to improve performance. Cortes et al [8] evaluate the parsing, string processing, memory allocation, thread overhead and overall capacity of a proxy.…”
Section: Related Workmentioning
confidence: 99%
“…Within the rate-based methods, downstream server has a consistent supervision over the rate of messages delivered from total upstream servers and informs its admissible rate to them [5,20]. In loss-based methods, downstream server repeatedly measures its current load and, accordingly, requests the upstream servers to reduce their transmitted load [21]. In window-based mechanisms, the load is not transmitted to the downstream server unless there are empty slots in upstream server window.…”
Section: Distributedmentioning
confidence: 99%
“…At 10 million concurrent connections, that amounts to 580 megabytes. In contrast, the Linux kernel uses in excess of 2 kilobytes per TCP connection [8]-not counting buffers for storing packet fragments. masscan is two orders of magnitude more efficient in its use of memory!…”
Section: B Memory Overheadmentioning
confidence: 99%