object - Designing for High Volumes of Data in an iPhone App -

I have an iPhone app that is about to display a table of data with about 25,000 records on opening needs. Has two fields: TITLE and DESCRIPTION. Both the fields are visible in each table cell. Table view can also be fully searchable with a UISearchBar.

When the application starts and the view loads, the "object object" grabs all the data from the table and loads it in "item objects" because I need both fields to search So I really have nothing to hydrate / dehydration; Thus, the entire table is in memory, in a better way, the full search capability should be provided, but at a time, the number of objects in memory is greatly reduced.

Any thoughts?

Edit:

I think I should be understood even more.

I'm already using a SQLite database. My problem is that it takes a lot of time to load 20,000 records in memory and this app looks sluggish

In addition, if I have 100 records on both sides of the current selection, how can I find all the records (which do not have memory)?

I see table representative suggestions.

You should use SQL instead of loading everything in the memory and searching Are there. What if you are using it like a flat file?

In addition, many applications have a "more load" entry, which is the last in their table view, which adds more items to the view.