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: Georg Tuparev <email@hidden>
- Date: Sun, 4 Dec 2005 14:47:30 +0100
On Dec 4, 2005, at 1:00 PM, Ruslan Zasukhin wrote:
On 12/4/05 11:00 AM, "Georg Tuparev" <email@hidden> wrote:
Hi Georg,
We need plug Valentina into that CoreData :-))
Then everything will work up to 100+ times faster
What we need is to stop making product advertisement. To mention once
a product is probably fine - to read about it 10 times in the last
week is like watching a bad TV channel...
Well, you think so, other developers have found this useful.
So what we will do?
I will try make future letters less like advertisement, okay?
Repeating like a broken gramophone that something is 100+ times
faster is neither scientifically sound nor very exiting for any
developer. Besides, I do not buy this as real fact... 100+ - if you
start calculating this - is more then the hardware could
theoretically allow... or you are talking about some extremely rare
cases without any statistical value. No one will complain if you
discuss technical questions, but just claims!?!?!
Besides, CoreData is not supposed to be used for enterprise
applications, but for simple application document store.
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. 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 :-) 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?
BTW, for the same app, but on the server site the test DB is 1.7TB
and average transaction takes 3-7s. Good enought, right?
During a week, on this list at least 2 developers have say:
we have problems.
So why we cannot show them other solution?
If you can show it - fine. But where is your solution? Ultra cool
replacement for CoreData bundled with Vodka? Somehow I am missing
this announcement...
Carefully thought and designed CoreData based app (as it is now)
works just
great.
Sorry, I not agree with you. When and if you meet big amount of
data, then
effective storage come into game. Even ideal design will take long
time on
gigabytes. Right?
Well, not. Data warehouse techniques are known for about 20 years -
people just do not like to learn them, and then blame hardware :-)
I love the ability to have XML store during early development,
and it is sufficiently well performing once in production (with
SQLl). IMHO, most of the performance problems discussed in this forum
are due to bad design...
And if you like to have enterprise application use completely
different architecture.
Nobody say about enterprise application here. You can easy get big
and huge
dbs even with desktop applications.
Could be ... only in my 30 years of software development I or any of
my clients (who include fortune 100 companies) never found the the
need to run Google DB on a laptop. I will love to see an exception.
later...
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
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