Re: CoreData - large data set is slow to load on app launch - optimization tips?
Re: CoreData - large data set is slow to load on app launch - optimization tips?
- Subject: Re: CoreData - large data set is slow to load on app launch - optimization tips?
- From: Ruslan Zasukhin <email@hidden>
- Date: Sun, 04 Dec 2005 18:26:47 +0200
- Thread-topic: CoreData - large data set is slow to load on app launch - optimization tips?
On 12/4/05 3:47 PM, "Georg Tuparev" <email@hidden> wrote:
Hi Georg,
>
> I believe that few days ago I have ask on this list:
>
>
>
> is CoreData supposed to be ONLY for simply things as
>
> preferences and e.g. storing of windows positions?
>
>
>
> Answer was -- CoreData can be used for something more complex.
>
>
And someone told you that you have no idea what you are talking about
>
but you preferred to ignore this. Position of windows and preferences
>
you store in NSUserDefaults.
I don't follow your logic here, Georg. I am agreeing above that CoreData is
for something more complex. Yes or no? If you think this is wrong, then just
disagree and say why. But instead you just make a direct personal attack on
me. This is the last letter I will answer from you in this way. I don't
think adults need to insult each other.
Your comment about Vodka is an ethnic slur: in the US they consider people
who say things like this racist. It seems to me, based on your name, you are
of Russian heritage. If you had some problem with Russia, vokda, kgb, etc
then excuse me, but I am not from Russia, and I don't ever drink vodka :-)
>
Here an example of what CoreData - just
>
doing this: a 20 GB large astronomical catalog spread in 50+ tables.
>
So far there is no query that takes me more then 1s - but I do not do
>
naive programming either :-)
I can easy show that your claims also can be taken negative.
* may be your db has 19.9 GB images?
* may be the most complex query you do is a simplest query as
select from T where ID = xx
then FYI, FileMaker also is very fast on such operation :-)
* even if divide 20Gb to 50+ tables this is only 300-400MB per table
including indexes (again what about images?).
* joins? group by ? Recursive joins ? No ?
>
Most importantly though, for client apps
>
it is the user experience that couts. If my UI can show 10 rows at a
>
time, why I need to fetch 100000000 and then complain that it is slow?
Hmm, you looks to be experienced developer but say strange things.
May be you do not know that often/sometimes. to get 10 records of result you
need make joins on several tables, then build GROUP BY, and so on ???
May be you do not know that even for 1-2 Gb it is possible to catch query
which work minutes (this words of my ISP friend about mySQL)
You happy with 1 second? Great. But somebody can wish 0.01 second.
------------
At last. It is interesting to listen people which use Windows, and which
have spend zero time on MacOS, that they are happy with Windows. It is fun
to see how changes their opinion after work with MacOS.
So I think its most valuable to hear the opinions of developers who try and
use many databases...not just Valentina, SQLite, mySQL.
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
_______________________________________________
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