I'd like to see the aio patch.  We evaluated several types early on but the
performance was not there and the writes were getting starved.  I'd expect
to see lots of testing under various loads and workloads.
On Mar 9, 2013 12:18 AM, "Yongming Zhao" <ming....@gmail.com> wrote:

> we have three big patches  on the way:
> 1, the SSD patch, which will implement the tiered storage mixed with SSD
> and ancient disks
> 2, SRV patch, we have a total rewrite on the SRV codes in the DNS and
> HostDB
> 3, the native AIO on Linux
>
> hopes we can make them ready in the following weeks, definitely we'd like
> them included in the V3.4 release.
>
> thanks
>
>
> 在 2013-3-9,上午9:50,Leif Hedstrom <zw...@apache.org> 写道:
>
> > Hi all,
> >
> > we had some good discussions on where we are today with 3.3.x, and how
> to get to v3.4.0 at the latest ApacheCon. This is a summary of what we want
> to achieve. Please read and comment.
> >
> > Thanks,
> >
> > -- leif and everyone who went to ACNA :)
> >
> >
> > Releases
> > =====
> >
> > Release date for v3.4.0: June - July 2013
> >    v3.3.1 - March 2013 (now)
> >    v3.3.2 - April 2013
> >    v3.3.3 - May 2013 - This is also Feature Freeze
> >    v3.3.4 - June 2013 (last release before v3.4.0)
> >
> >
> > Toolchain
> > ======
> >
> > The minimum/platform requirements for building v3.4.0 are
> >
> >    * gcc v4.1.2 (RHEL5) or compatible
> >    * clang v3.x and Intel CC (v12 or later)
> >    * Linux v2.6.18 or later (RHEL5)
> >    * FreeBSD, OSX and Solaris (e.g. OmniOS) supported
> >    * x86, x86_64 and ARM supported
> >    * In particular, we drop support for the SunStudio compiler suite,
> and RHEL4 and earlier
> >
> >
> > Features
> > =====
> >
> > The focus are on the following improvement over v3.2.x:
> >
> >    * Close as many instability bugs as possible
> >
> >    * Land SSD layered cache (aim for v3.3.2)
> >
> >    * Volumes assigned to disks (aim for v3.3.2) [Comcast]
> >
> >    * Time Wheel patch [Taobao]
> >
> >    * Memory allocation [Yahoo and Taobao]
> >
> >    * Range requests / lookup table (well tested)
> >
> >    * More unit tests
> >
> >    * Documentation - We really suffer here, it'd be great to make a push
> for v3.4.0 docs
> >
>
>

Reply via email to