Is Core-Data so slow with fetch?
Is Core-Data so slow with fetch?
- Subject: Is Core-Data so slow with fetch?
- From: malcom <email@hidden>
- Date: Tue, 28 Mar 2006 20:40:32 +0200
Hello, I'm making a newsgroup client. I would to use Core-Data to
store article's data for each signed groups.
My first attempt was to create a modeled object like this:
<http://www.rietiforum.com/imageupload//images/7960xcode.png>
So I've an entity called Article with some attributes (the main
information about an article, to get better performances) and some
releationships: father (releationship to another Article entity),
childs (to-many releationship to Article), header (to-many
releationship that contains each article header), and a body
releationship that link to a Body entity with the text of a message.
It seems pretty simple and good, I hope, but unfortunatly still very
slow. Using SQLite store the first fetch to db for a single object
(*single* not all articles entitites!!!) takes about 10 secs! (the
other fetchs seems to be pretty fast on my macbook).
My database contains about 8,000 records (but teorically it should
contains at least 20,000 in a normal usage) and it's about 50mb
weight.
Is core-data so slow or is there a problem with my modeled object?
A possible solution could be to load a persistent store with a list of
articles + headers and another db that contains only the articles. But
it's not so elegant and I'm not sure that it handle to my problem.
Anyone can help me with this teorically-fantastic new technology?
Thanks a lot.
malcom
_______________________________________________
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