> On Apr 6, 2016, at 7:43 AM, James Cicenia <[email protected]> wrote: > > What is the magic combination of options to send to the sqlite to completely > turn off journaling. > I have an initialization on install that brings down a lot of data. I don’t > need journaling at this point > and it balloons the memory storage upon install to over 500MB!
Journaling doesn’t affect memory usage, except in the ‘memory’ mode or if the database is entirely in-memory, both of which seem unlikely for Core Data. I would imagine that Core Data uses the WAL mode since it’s significantly more efficient than the older journaling modes. If you’re seeing high memory utilization, it’s more likely something to do with Core Data itself. It might be a symptom of a way you’re misusing Core Data, but my knowledge of that API is very old and rusty so I don’t have any advice there. Have you tried using Instruments or the ‘heap’ tool to look at allocation patterns when this occurs? You should be able to tell the difference between SQLite allocations (which will be anonymous malloc blocks) and Core Data allocations (which will be Obj-C objects.) —Jens _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
