From Tim.Haley@sun.com Fri Aug 7 14:27:53 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n77LRqfi023449 for ; Fri, 7 Aug 2009 14:27:52 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n77LRdI6027922; Sat, 8 Aug 2009 05:27:51 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KO000M0JZMDOP00@brm-avmta-1.central.sun.com>; Fri, 07 Aug 2009 15:27:49 -0600 (MDT) Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KO0002IGZMCAQ90@brm-avmta-1.central.sun.com>; Fri, 07 Aug 2009 15:27:48 -0600 (MDT) Received: from spidey.local (spidey.Central.Sun.COM [172.20.25.27]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n77LRmmr012997; Fri, 07 Aug 2009 15:27:48 -0600 (MDT) Received: from spidey.local (localhost [127.0.0.1]) by spidey.local (8.14.3+Sun/8.14.3) with ESMTP id n77LJRrv007955; Fri, 07 Aug 2009 15:19:27 -0600 (MDT) Received: (from timh@localhost) by spidey.local (8.14.3+Sun/8.14.3/Submit) id n77LJRbd007954; Fri, 07 Aug 2009 15:19:27 -0600 (MDT) Date: Fri, 07 Aug 2009 15:19:27 -0600 (MDT) From: Tim Haley Subject: ZFS logbias property [PSARC/2009/423 Self Review] To: PSARC-ext@sun.com Cc: zfs-team@sun.com Message-id: <200908072119.n77LJRbd007954@spidey.local> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3350 I am sponsoring the following case on behalf of Neil Perrin. Requested binding is Micro/Patch. The case is a straight-forward addition of a new property on zfs datasets for tuning separate intent log usage. I believe the case qualifies for self review and have filed it as closed approved automatic. If folks disagree, let me know and I'll convert it to a fast-track. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: ZFS logbias property 1.2. Name of Document Author/Supplier: Author: Neil Perrin 1.3 Date of This Document: 07 August, 2009 4. Technical Description Summary Provide zfs with the ability to control the use of resources used for synchronous (eg fsync, O_DSYNC) requests. In particular it enables substantially better performance for Oracle and potentially other applications. Background Oracle manages two major types of files, the Data Files and the Redo Log files. Writes to Redo Log files are in the path of all transactions and low latency is a requirement. It is critical for good performance to give high priority to these write requests. Data Files are also the subject of writes from DB writers as a form of scrubbing dirty blocks to insure DB buffer availability. Write latency is much less an issue. Of more more importance is achieving an acceptable level of throughput. These writes are less critical to delivered performance. Both types of writes are synchronous (using O_DSYNC), and thus treated equally. They compete for the same resources: separate intent log, memory, and normal pool IO. The Data File writes impede the potential performance of the critical Redo Log writers. Proposal Create a new "logbias" property for zfs datasets. If logbias is set to 'latency' (the default) then there is no change from the current implementation. If the logbias property is set to 'throughput' then intent log blocks will be allocated from the main pool instead of any separate intent log devices (if present). Also data will be written immediately to spread the write load thus making for quicker subsequent transaction group commits to the pool. To change the property, an admin will use the standard zfs set command: # zfs set logbias=latency {dataset} # zfs set logbias=throughput {dataset} The current value of logbias can be retrieved in the normal manner with 'zfs get logbias' or 'zfs list -o logbias'. Manpage diffs --- old=09Thu May 7 15:41:08 2009 +++ new=09Thu May 7 15:44:30 2009 @@ -1038,7 +1038,15 @@ perty was changed. If the new property is "off", the file systems are unshared. + logbias = latency | throughput + + Provide a hint to ZFS about handling of synchronous + requests in this dataset. If logging is set to "latency" (the + default) ZFS will use pool log devices (if configured) to handle the + requests at low latency. If logging is set to "throughput" then ZFS + will not use configured pool log devices. ZFS will + instead optimize synchronous operations for global + pool throughput and efficient use of resources. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From gdamore@sun.com Fri Aug 7 14:42:49 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n77LgmQR023556 for ; Fri, 7 Aug 2009 14:42:49 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n77LgcjE004701; Sat, 8 Aug 2009 05:42:47 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KO100F050B82400@nwk-avmta-1.sfbay.Sun.COM>; Fri, 07 Aug 2009 14:42:44 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KO1004UX0B8JL60@nwk-avmta-1.sfbay.Sun.COM>; Fri, 07 Aug 2009 14:42:44 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n77LgiOU029389; Fri, 07 Aug 2009 14:42:44 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KO000I00ZYV3L00@fe-sfbay-09.sun.com>; Fri, 07 Aug 2009 14:42:44 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KO100IXT0AJ8O20@fe-sfbay-09.sun.com>; Fri, 07 Aug 2009 14:42:20 -0700 (PDT) Date: Fri, 07 Aug 2009 14:42:19 -0700 From: "Garrett D'Amore" Subject: Re: ZFS logbias property [PSARC/2009/423 Self Review] In-reply-to: <200908072119.n77LJRbd007954@spidey.local> Sender: Garrett.Damore@sun.com To: Tim Haley Cc: PSARC-ext@sun.com, zfs-team@sun.com Message-id: <4A7C9FBB.3020508@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200908072119.n77LJRbd007954@spidey.local> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 4091 In my opinion it pushes the boundaries of what is appropriate for a self-review, since this represents a potentially significant new behavior that will be exposed to customers and ISVs. However, it also looks fairly obvious and straight-forward. Can I kindly request that you promote this to a fast track, and accept my +1 at the same time? (Unless someone else has some significant concern, the only negative implication of this is that you'll need to wait a few days before integrating ... probably this will be approved on Wednesday.) - Garrett Tim Haley wrote: > I am sponsoring the following case on behalf of Neil Perrin. > Requested binding is Micro/Patch. The case is a straight-forward > addition of a new property on zfs datasets for tuning separate > intent log usage. I believe the case qualifies for self review and > have filed it as closed approved automatic. If folks disagree, let me > know and I'll convert it to a fast-track. > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > ZFS logbias property > 1.2. Name of Document Author/Supplier: > Author: Neil Perrin > 1.3 Date of This Document: > 07 August, 2009 > > 4. Technical Description > > Summary > > Provide zfs with the ability to control the use of resources > used for synchronous (eg fsync, O_DSYNC) requests. In particular > it enables substantially better performance for Oracle and > potentially other applications. > > Background > > Oracle manages two major types of files, the Data Files and the Redo Log > files. Writes to Redo Log files are in the path of all transactions > and low latency is a requirement. It is critical for good performance > to give high priority to these write requests. > > Data Files are also the subject of writes from DB writers as a form of > scrubbing dirty blocks to insure DB buffer availability. Write latency is > much less an issue. Of more more importance is achieving an acceptable level > of throughput. These writes are less critical to delivered performance. > > Both types of writes are synchronous (using O_DSYNC), and thus treated > equally. They compete for the same resources: separate intent log, > memory, and normal pool IO. The Data File writes impede the potential > performance of the critical Redo Log writers. > > Proposal > > Create a new "logbias" property for zfs datasets. > > If logbias is set to 'latency' (the default) then there is no change from the > current implementation. If the logbias property is set to 'throughput' > then intent log blocks will be allocated from the main pool instead of any > separate intent log devices (if present). Also data will be written > immediately to spread the write load thus making for quicker subsequent > transaction group commits to the pool. > > To change the property, an admin will use the standard zfs set command: > > # zfs set logbias=latency {dataset} > # zfs set logbias=throughput {dataset} > > The current value of logbias can be retrieved in the normal > manner with 'zfs get logbias' or 'zfs list -o logbias'. > > Manpage diffs > > --- old=09Thu May 7 15:41:08 2009 > +++ new=09Thu May 7 15:44:30 2009 > @@ -1038,7 +1038,15 @@ > perty was changed. If the new property is "off", the > file systems are unshared. > > + logbias = latency | throughput > + > + Provide a hint to ZFS about handling of synchronous > + requests in this dataset. If logging is set to "latency" (the > + default) ZFS will use pool log devices (if configured) to handle the > + requests at low latency. If logging is set to "throughput" then ZFS > + will not use configured pool log devices. ZFS will > + instead optimize synchronous operations for global > + pool throughput and efficient use of resources. > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: Automatic > 6.6. ARC Exposure: open > > From tim.haley@sun.com Fri Aug 7 14:53:38 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n77LrbfK023672 for ; Fri, 7 Aug 2009 14:53:37 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n77LrZEo010014; Fri, 7 Aug 2009 22:53:36 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KO1002010TCDJ00@brm-avmta-1.central.sun.com>; Fri, 07 Aug 2009 15:53:36 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KO1002N70TBADA0@brm-avmta-1.central.sun.com>; Fri, 07 Aug 2009 15:53:35 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n77LrZAG008146; Fri, 07 Aug 2009 21:53:35 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KO1008000PXJB00@mail-amer.sun.com>; Fri, 07 Aug 2009 15:53:35 -0600 (MDT) Received: from [172.20.25.27] ([unknown] [172.20.25.27]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KO100AR90TA4LD0@mail-amer.sun.com>; Fri, 07 Aug 2009 15:53:35 -0600 (MDT) Date: Fri, 07 Aug 2009 15:52:44 -0600 From: Tim Haley Subject: ZFS logbias property [PSARC/2009/423 FastTrack timeout 08/14/2009] In-reply-to: <4A7C9FBB.3020508@sun.com> Sender: Timothy.Haley@sun.com To: "Garrett D'Amore" Cc: PSARC-ext@sun.com, zfs-team@sun.com Message-id: <4A7CA22C.6010501@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200908072119.n77LJRbd007954@spidey.local> <4A7C9FBB.3020508@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 4336 Garrett D'Amore wrote: > In my opinion it pushes the boundaries of what is appropriate for a > self-review, since this represents a potentially significant new > behavior that will be exposed to customers and ISVs. > > However, it also looks fairly obvious and straight-forward. > > Can I kindly request that you promote this to a fast track, and accept > my +1 at the same time? > > (Unless someone else has some significant concern, the only negative > implication of this is that you'll need to wait a few days before > integrating ... probably this will be approved on Wednesday.) > > - Garrett > Sure. I've changed the IAM file and set the timeout for 8/14. -tim > Tim Haley wrote: >> I am sponsoring the following case on behalf of Neil Perrin. >> Requested binding is Micro/Patch. The case is a straight-forward >> addition of a new property on zfs datasets for tuning separate >> intent log usage. I believe the case qualifies for self review and >> have filed it as closed approved automatic. If folks disagree, let me >> know and I'll convert it to a fast-track. >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> ZFS logbias property >> 1.2. Name of Document Author/Supplier: >> Author: Neil Perrin >> 1.3 Date of This Document: >> 07 August, 2009 >> >> 4. Technical Description >> >> Summary >> >> Provide zfs with the ability to control the use of resources >> used for synchronous (eg fsync, O_DSYNC) requests. In particular >> it enables substantially better performance for Oracle and >> potentially other applications. >> >> Background >> >> Oracle manages two major types of files, the Data Files and the Redo Log >> files. Writes to Redo Log files are in the path of all transactions >> and low latency is a requirement. It is critical for good performance >> to give high priority to these write requests. >> >> Data Files are also the subject of writes from DB writers as a form of >> scrubbing dirty blocks to insure DB buffer availability. Write latency is >> much less an issue. Of more more importance is achieving an acceptable >> level >> of throughput. These writes are less critical to delivered performance. >> >> Both types of writes are synchronous (using O_DSYNC), and thus treated >> equally. They compete for the same resources: separate intent log, >> memory, and normal pool IO. The Data File writes impede the potential >> performance of the critical Redo Log writers. >> >> Proposal >> >> Create a new "logbias" property for zfs datasets. >> >> If logbias is set to 'latency' (the default) then there is no change >> from the >> current implementation. If the logbias property is set to 'throughput' >> then intent log blocks will be allocated from the main pool instead of >> any >> separate intent log devices (if present). Also data will be written >> immediately to spread the write load thus making for quicker subsequent >> transaction group commits to the pool. >> >> To change the property, an admin will use the standard zfs set command: >> >> # zfs set logbias=latency {dataset} >> # zfs set logbias=throughput {dataset} >> >> The current value of logbias can be retrieved in the normal >> manner with 'zfs get logbias' or 'zfs list -o logbias'. >> >> Manpage diffs >> >> --- old=09Thu May 7 15:41:08 2009 >> +++ new=09Thu May 7 15:44:30 2009 >> @@ -1038,7 +1038,15 @@ >> perty was changed. If the new property is "off", the >> file systems are unshared. >> >> + logbias = latency | throughput >> + >> + Provide a hint to ZFS about handling of synchronous >> + requests in this dataset. If logging is set to "latency" (the >> + default) ZFS will use pool log devices (if configured) to handle the >> + requests at low latency. If logging is set to "throughput" then ZFS >> + will not use configured pool log devices. ZFS will >> + instead optimize synchronous operations for global >> + pool throughput and efficient use of resources. >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> ON >> 6.5. ARC review type: Automatic >> 6.6. ARC Exposure: open >> >> > From tim.haley@sun.com Wed Aug 12 10:13:38 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n7CHDcfI011567 for ; Wed, 12 Aug 2009 10:13:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n7CHDDuj011637 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 12 Aug 2009 18:13:37 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KO90051FX6NLP00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 12 Aug 2009 11:13:35 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KO90028IX6MF840@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 12 Aug 2009 11:13:34 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n7CHDYAw010387 for ; Wed, 12 Aug 2009 17:13:34 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KO900L00VOAQ000@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 12 Aug 2009 11:13:34 -0600 (MDT) Received: from [172.20.25.27] ([unknown] [172.20.25.27]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KO900JRJX64JD90@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 12 Aug 2009 11:13:21 -0600 (MDT) Date: Wed, 12 Aug 2009 11:12:28 -0600 From: Tim Haley Subject: Re: ZFS logbias property [PSARC/2009/423 FastTrack timeout 08/14/2009] In-reply-to: <4A7CA22C.6010501@sun.com> Sender: Timothy.Haley@sun.com To: PSARC-ext@sun.com Message-id: <4A82F7FC.6030806@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200908072119.n77LJRbd007954@spidey.local> <4A7C9FBB.3020508@sun.com> <4A7CA22C.6010501@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 60 This case was approved in today's (08/12/09) PSARC meeting.