Re: [rtcweb] Audio transcoding: CPU costs
"Espen Berger (espeberg)" <espeberg@cisco.com> Thu, 14 March 2013 21:29 UTC
Return-Path: <espeberg@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8982B11E8191 for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 14:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ky09BZXHblJ for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 14:29:15 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9076011E814D for <rtcweb@ietf.org>; Thu, 14 Mar 2013 14:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1868; q=dns/txt; s=iport; t=1363296555; x=1364506155; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aw/x1Mm5XlT52zuWz8D1Jbpb4iRbMvpVlKAZHB1INlI=; b=lWVqDev/yi8daK0z86/DOM0r9EgRm0HYg7Uub6L1mWZtwTQNQIxA3I0s EMNrU9fhJYLPFnbhTp8ICqLL0ZfbA+7CQqy0xzimnA4aASupybFxnCWAS GOWmsJ1d4+NjfEw3nFnt3/P7+JUBXed6NiBXgPXbOjZp6ghCvOYIcq95S s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAMk/QlGtJXHA/2dsb2JhbABDxQKBZRZ0gisBAQEEAQEBNzQLDAQCAQgRBAEBAQoUCQcnCxQJCAIEAQ0FCIgMDMIJjmUxBwaCWWEDp1qDCoIo
X-IronPort-AV: E=Sophos;i="4.84,846,1355097600"; d="scan'208";a="187412498"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 14 Mar 2013 21:29:14 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2ELTDsu019634 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Mar 2013 21:29:13 GMT
Received: from xmb-rcd-x11.cisco.com ([169.254.1.206]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 16:29:13 -0500
From: "Espen Berger (espeberg)" <espeberg@cisco.com>
To: Jean-Marc Valin <jmvalin@mozilla.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] Audio transcoding: CPU costs
Thread-Index: AQHOIEcKbSPQS+qPR0i9uWInpsZm+pik9cCAgAAIH4CAALKJcA==
Date: Thu, 14 Mar 2013 21:29:12 +0000
Message-ID: <E8F5F2C7B2623641BD9ABF0B622D726D0F6A7DB2@xmb-rcd-x11.cisco.com>
References: <5141133D.3040100@alvestrand.no> <CAD5OKxvqbWYCb8f8_M14yqhk-OYxtVmhp6xKmWuyiaNSaSLAmQ@mail.gmail.com> <514160E7.1090205@mozilla.com>
In-Reply-To: <514160E7.1090205@mozilla.com>
Accept-Language: nb-NO, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.89.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Audio transcoding: CPU costs
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 21:29:16 -0000
Transcoding is not the only cost when mapping from one audio codec to another one in some infrastructure component. * You need to re-encrypt to get secure calls * Map between resilience techniques from different codecs * Rate adaptation from one bitrate to another -Espen -----Original Message----- From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Jean-Marc Valin Sent: 14. mars 2013 06:32 To: Roman Shpount Cc: rtcweb@ietf.org Subject: Re: [rtcweb] Audio transcoding: CPU costs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/14/2013 01:03 AM, Roman Shpount wrote: > 1. Based on the message you are quoting, current performance is > 150 channels per core. It would require some non-trivial work to get > it to 500 channels. Yeah, it'd probably take 2-3 weeks to write some assembly. Also, keep in mind that these numbers were measured using a single core of a laptop that just turned three years old (http://ark.intel.com/products/43560/Intel-Core-i7-620M-Processor-4M-Cache-2_66-GHz). I would expect your servers to have slightly more powerful CPUs :-) Jean-Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRQWDnAAoJEJ6/8sItn9q9/IAIAKxX5xG8ACKxhQrlMLjhD1eX uhITi8mVOiE3wGuBbdge4JzAs7IlmJ+Db7sp0w7INmv8G0GgmOT44c3wZgU7l6LF k5wKE6/UzCC+tFBtLVfuMJtvnswrjPEQvHkp9mM0U4sA1RBzIMv9NyCymt/zgQtG 3jlH9Tr9oD4n5Ug90UbRlF52cT5yfPL+nsDflCPhEcDvsnseckLQtO0N+kIBgabH 9MWh9sq3RFzwtE4iWq5vdzlhWnPd0qp7bAWa8flMA4DAfcgaYkXMh/N8ejo/zo0e SAkL6jlMm259Nnl3fTVtD0SdPKTPUckRNuggai/GfHsgCrAFz0ua8sePyiQXZgg= =yLLG -----END PGP SIGNATURE----- _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Audio transcoding: CPU costs Harald Alvestrand
- Re: [rtcweb] Audio transcoding: CPU costs Roman Shpount
- Re: [rtcweb] Audio transcoding: CPU costs Jean-Marc Valin
- Re: [rtcweb] Audio transcoding: CPU costs Espen Berger (espeberg)
- Re: [rtcweb] Audio transcoding: CPU costs Harald Alvestrand