lkml.org 
[lkml]   [2012]   [Oct]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 00/16] f2fs: introduce flash-friendly file system
    On Tue, Oct 09, 2012 at 02:53:26PM -0500, Jooyoung Hwang wrote:

    > I'd like you to refer to the following link as well which is about
    > mobile workload pattern.
    > http://www.cs.cmu.edu/~fuyaoz/courses/15712/report.pdf
    > It's reported that in Android there are frequent issues of fsync and
    > most of them are only for small size of data.

    What bothers me is no one is asking the question, *why* is Android
    (and more specifically SQLite and the applications which call SQLite)
    using fsync's so often? These aren't transaction processing systems,
    after all. So there are two questions that are worth asking here.
    (a) Is SQLite being as flash-friendly as possible, and (b) do the
    applications really need as many transaction boundaries as they are
    requesting of SQLite.

    Yes, we can optimize the file system, but sometimes the best way to
    optimize a write is to not to do the write at all (if it is not
    required for the application's functionality, of course). If the
    application is requesting 4 transaction boundaries where only one is
    required, we can try to make fsync's more efficient, yes --- but there
    is only so much that can be done at the fs layer.

    - Ted


    \
     
     \ /
      Last update: 2012-10-10 11:41    [W:3.514 / U:0.096 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site