From owner-freebsd-stable@FreeBSD.ORG Wed Jun 6 00:16:55 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D4951065670 for ; Wed, 6 Jun 2012 00:16:55 +0000 (UTC) (envelope-from scottl@netflix.com) Received: from exout104.netflix.com (exout102.netflix.com [69.53.237.163]) by mx1.freebsd.org (Postfix) with ESMTP id 3254C8FC14 for ; Wed, 6 Jun 2012 00:16:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=s1024;d=netflix.com; h=from:to:cc:subject:date:message-id:references:in-reply-to :content-type:mime-version; bh=sivi140IM5fdDVQ2lWtXkY9LuEQ=; b=ZH1l+hP9HWH4JvaNLS+Bi3ymFu8DOoJdHIUDyvpNSrkYSY1ebW+N6x6zGsPgpbJIzlM3Vi9w NfYJWfp9IBUx+LLbBipOALvW9rrbGG2IEB8R5Jv7VnnjgCt8rH2fSQOiHwBNAIVmYdd7Xabz wJ7VzNq6onRrqm/k4o5uaNweyJE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;d=netflix.com; h=from:to:cc:subject:date:message-id:references:in-reply-to :content-type:mime-version; b=SIT/2n7VKws+iqypSU7N9mOJkoRFzeYf/v+RlTOxuiVJGz1yPHjZ6o9v6OaX6eEVq81iczVd t+ncyf5TtleB0dMLOj0gvVq8mxNp7oOVxKGI7d3q5k+V2/FO6laqWXTXG6aQSBXGD3X46mGr yKZ4R/KGfUAzkXhmOQlDLyxzdwk= Received: from EXFE101.corp.netflix.com (10.64.32.161) by exout104.netflix.com (10.64.240.74) with Microsoft SMTP Server (TLS) id 14.2.298.4; Tue, 5 Jun 2012 17:16:50 -0700 Received: from EXMB107.corp.netflix.com ([169.254.7.134]) by exfe101.corp.netflix.com ([10.64.32.161]) with mapi id 14.02.0283.003; Tue, 5 Jun 2012 17:16:48 -0700 From: Scott Long To: Benjamin Francom Thread-Topic: Netflix's New Peering Appliance Uses FreeBSD Thread-Index: AQHNQ3mpDyhfu/u2jUaowYKh4kcMDQ== Date: Wed, 6 Jun 2012 00:16:46 +0000 Message-ID: <3CEF3B39-BE1E-4FC4-81F3-D26049C83313@netflix.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.64.24.140] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-stable@freebsd.org" Subject: Re: Netflix's New Peering Appliance Uses FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 00:16:55 -0000 On Jun 5, 2012, at 9:56 AM, Benjamin Francom wrote: > I just saw this, and thought I'd share: >=20 > Open Connect Appliance Software >=20 > Netflix delivers streaming content using a combination of intelligent > clients, a central control system, and a network of Open Connect applianc= es. >=20 > When designing the Open Connect Appliance Software, we focused on these > fundamental design goals: >=20 > - Use of Open Source software > - Ability to efficiently read from disk and write to network sockets > - High-performance HTTP delivery > - Ability to gather routing information via BGP >=20 > Operating System >=20 > For the operating system, we use FreeBSD versio= n > 9.0. This was selected for its balance of stability and features, a stron= g > development community and staff expertise. We will contribute changes we > make as part of our project to the community through the FreeBSD committe= rs > on our team. > Web server >=20 Yes, we are indeed using FreeBSD at Netflix! For those who are interested,= I recently moved from Yahoo to Netflix to help support FreeBSD for them, and I'm definitely impressed with what is going on there. Other than a few sma= ll changes, we're using stock FreeBSD 9, tracking the 9-stable branch on a regular basis. Our chassis is a semi-custom 4U 19" form factor with thirty= six 3TB SATA disks and 2 SSDs. Each disk has its own UFS+J filesystem, except = for the SSDs that are mirrored together with gmirror. The SSDs hold the OS ima= ge and cache some of the busiest content. The other disks hold nothing but th= e audio and video files for our content streams. We connect to the outside w= orld via a twin-port Intel 10GBe optical NIC (only one port is active at the mom= ent), and we use LSI MPT2 controllers for 32 of the 36 disks. The other 4 disks connect to the onboard AHCI SATA controller. All of the disks are direct-attach with no SAS backplanes or expanders. Out-of-band management happens via IPMI on an on-board 1Gb NIC. The entire system consumes around 500W of power, making it a very efficient appliance for its function= ality. Netflix is also at the front of the internet pack with IPv6 roll-out, and F= reeBSD plays an essential part of that. We've been working hard on stabilizing th= e FreeBSD IPv6 stack for production-level traffic, and I recommend that all u= sers of IPv6 update to the latest patches in 9-stable and 8-stable. Contact me directly if you have questions about this. That said, we're excited about = World IPv6 Day, and we're ready with AAAA DNS records and content service from bo= th Amazon and the traditional CDNs as well as our OpenConnect network. >From an advocacy standpoint, Netflix represents 30% of all North American internet traffic during peak hours, and FreeBSD is becoming an integral par= t of that metric as we shift traffic off of the traditional CDNs. We're expa= nding quickly, which means that FreeBSD is once again a core part of the internet infrastructure. As we find and fix stability and performance issues, we're aggressively pushing those changes into FreeBSD so that everyone can benefit from them, just as we benefit from the contributions of the rest of= the FreeBSD ecosystem. We're proud to be a part of the community, and look forward to a long-term relationship with FreeBSD. If you have any questions, let me know or follow the information links on t= he OpenConnect web site. Scott