These figures pale into insignificance compared to the power required for standard SIP devices - typically 5-8 watts per device multiplied by the number of devices. When you factor in Gigabit Ethernet the power ups significantly. Optimisation at the server level is not significant on any scale. Optimisation on communications power: i.e. end-devices, DSL & switches is where the power savings are important.

These figures pale into insignificance compared to the power required for standard SIP devices - typically 5-8 watts per device multiplied by the number of devices. When you factor in Gigabit Ethernet the power ups significantly. Optimisation at the server level is not significant on any scale. Optimisation on communications power: i.e. end-devices, DSL & switches is where the power savings are important. Daniel-Constantin Mierla wrote: _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On Wed, May 25, 2011 at 06:54, Jeremya<jeremy(a)electrosilk.net> wrote: Sure, the total power consumption of the whole system is dominated by the power consumption of end-point devices, there's no doubt about that and the paper says that. Nevertheless, as an ITSP you are typically paying for the energy consumed by your servers and in that case knowing what you can expect and how many servers you need is useful. Modern data-center servers have significant base-line power consumption and a portion of that needs to be attributed to the SIP service running on those servers. -Jan _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On Wed, May 25, 2011 at 06:54, Jeremya <jeremy(a)electrosilk.net> wrote: Sure, the total power consumption of the whole system is dominated by the power consumption of end-point devices, there's no doubt about that and the paper says that. Nevertheless, as an ITSP you are typically paying for the energy consumed by your servers and in that case knowing what you can expect and how many servers you need is useful. Modern data-center servers have significant base-line power consumption and a portion of that needs to be attributed to the SIP service running on those servers.

> Daniel-Constantin Mierla wrote: >> Hello, >> >> Jan Janak conducted a very interesting research project regarding >> energy efficiency of VoIP systems during 2010, a collaboration between >> iptel.org and Columbia University. >> >> The team used the source code from sip-router.org GIT repository from >> January 2010, which corresponds to Kamailio (former OpenSER) and SER >> v3.0. The latest stable series v3.1 shares the same internal >> architecture with v3.0. >> >> As part of the research work, Jan could also gather some figures about >> capacity and performances of v3.0 with a quite complex configuration >> file: etc/sip-router-oob.cfg (involving authentication and NAT >> traversal as well). >> >> You can read the paper about energy efficiency at: >> >> - Green VoIP Article: http://asipto.com/u/2j >> >> The draft notes about capacity and performances of v3.0 are available at: >> >> - Performances and Capacity for v3.0 Wiki page: http://asipto.com/u/2k >> >> Some interesting results: >> >> - one instance of SIP server with 500 000 online users (mixed users – >> behind and not NAT routers) – consumed energy 210W >> - one instance of SIP server with 1 000 000 online users (no NAT >> involved) – consumed energy 190W >> - on a 32-bit machine with 4GB of memory and with 2.5GB reserved for >> SIP server, the server could support 43 000 simultaneous TLS >> connections – consumed energy 203W >> - one SIP server instance with 80 000 permanent TCP connections, the >> SIP server could still handle at least 1000 requests per second and a >> connection arrival rate of 1000 new connections per second, done for >> 20 000 new connections. CPU load generated by the SIP server was from >> 6% to 8%. >> >> I added a new section to the draft notes to list the enhancements done >> for the latest stable release (v3.1.x) that contribute to performance >> improvements, like asynchronous TLS, fine tuning of memory for TLS >> connections and raw UDP sockets. >> >> Cheers, >> Daniel