Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: bad fsync? (A.M.)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bad fsync? (A.M.)



If you haven't already, try:

PRAGMA synchronous = OFF;

In my experience OS X take a much more significant hit for fsync calls than other systems. As far as I can tell there isn't a whole lot of benefit in calling fsync alone since it has no effect on the actual drive cache. Sqlite works quite a bit better with synchronous (fsync) disabled and there isn't any increase in data exposure.

I'm sure you have seen this regarding the benefit of transactions: http://www.sqlite.org/speed.html

FYI

-Jon

On Feb 21, 2005, at 11:58 AM, James Berry wrote:

Dominic,

Thanks for a great explanation. A similar thread has come up on the sqlite list, claiming that using F_FULLFSYNC leads to dramatic performance decreases on Darwin over other platforms. Any thoughts on these issues?

    From:       email@hidden
    Subject:     [sqlite] sluggish operation on os x?
    Date:     February 21, 2005 12:44:03 AM PST
    To:       email@hidden
    Reply-To:       email@hidden

Finally getting my SQLite3 code working, I'm experiencing awfully slow performance when writing individual data on OS X.

Linux (Ubuntu) is lightning fast, Win32 is.. tolerable, but OS X really crawls. I've tried both with built-in sources, and the new SQLite3 fink module. Same behaviour.


_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: bad fsync? (A.M.) (From: Dominic Giampaolo <email@hidden>)
 >Re: bad fsync? (A.M.) (From: James Berry <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.