Re: [Core Data] Improve save performance ?
Re: [Core Data] Improve save performance ?
- Subject: Re: [Core Data] Improve save performance ?
- From: Eric Morand <email@hidden>
- Date: Tue, 17 Jan 2006 00:01:10 +0100
Thanks to both of you for the explanation. I'll try to learn using
Shark...
For now, I have some news : I've created a test Core Data app, with
the same managed object model than my official app.
I've then tries to save an object (of the same entity than the one
that takes so much time to save on my app) using an SQLite persistent
store and an XML one.
Here are the results :
- SQLite : around 0.450 second
- XML : around 0.005 second !!!
In my case an XML persistent store is around 100 times faster than
SQLite !!!??? Is this normal ?
Maybe there is something I'm doing wrong when creating my SQLite
persistent store. I thought a SQLite store was faster than XML store.
Ideas ?
Eric.
Le 16 janv. 06 à 23:19, Scott Ellsworth a écrit :
On Jan 16, 2006, at 2:01 PM, Eric Morand wrote:
I'm ashamed to admit that I don't know how to use Shark...
It is worth learning. Apple has run one and two hour sessions at
WWDC and at various Tiger previews that went over the details.
There is a page at <http://developer.apple.com/tools/
shark_optimize.html> that gives a reasonable overview of the
optimization process. <http://developer.apple.com/performance/
appperformance.html> is also a good set of hints, and it has links
to the pages where Apple goes into some detail.
A quick start: bring up your project in xcode after installing the
performance tools. (IIRC, they are installed by default by the
xcode 2.2 installers, so if you have XCode 2.2, you almost
certainly have shark in /Developer/Applications/Performance Tools.)
In the debug menu, select 'launch with performance tool'
Accept the defaults, then after switching to your app and starting
teh time consuming part of your process, hit cmd-esc. Once the
time consuming part is done, hit it again
By default, it stops sampling after thirty seconds, so if you can
make the time consuming part take about thirty seconds, then you
have both a clear test case, and an easier sample.
You will almost certainly then need to spend some time at the pages
above once it gets complicated, but shark is your friend.
Scott
---
email@hidden
Java, Cocoa, Tapestry, and Database Consulting
Currently seeking new contracts - inquire within
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
=============================================
Automator Ketchup : http://automatorketchup.blogspot.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden