ios - How to effectively deal with large datasets in Core Data? -


i using core data in app store entities have many 50k objects or more. have paired nsfetchedresultscontroller in table view. table view works fine due cell reuse biggest problem queuring actual database dataset.

when first load table view need results db. using default fetch request single sort descriptor , have set batchsize 1,000. on ipad 2 query takes 15 secs finish! have run query after search has been cancelled overall makes app unusable. assumption cd still has resolve results or setup sections or something, have no idea using batchsize doesn't help?? content dynamic in sense new rows getting added, sort order changing etc.. caching has limited benefit.

i thinking best option use fetchlimit in fetchrequest , implement basic paging. when table view scrolls end fetch next "page" of results? problem approach lose sectionindex , cant think of way around that.

anyone have ideas or dealt issue already?

when set fetch request frc batch size should few items bigger than, maybe twice size as, number of items can seen on screen @ 1 time. frc pagination you need set page size better.


Comments

Popular posts from this blog

php - Calling a template part from a post -

Firefox SVG shape not printing when it has stroke -

How to mention the localhost in android -