SQLite pagination limits and memory overhead in Titanium

Dataset Retrieval Constraints

Managing large local datasets in Appcelerator Titanium requires balancing SQLite query efficiency with the memory constraints of the JavaScript runtime. While the database driver supports standard SQL clauses for bounding result sets, the process of mapping native records to JavaScript objects can introduce significant overhead.

Performance Trade-offs

Using LIMIT and OFFSET allows for the implementation of paginated lists, but performance typically degrades as the offset increases because the engine must still scan through the skipped rows. There is a critical threshold where retrieving larger chunks of records may lead to memory pressure or application instability during the native-to-JS bridge transfer.

• Impact of high offset values on query execution time.
• Memory consumption when mapping large result sets to JS objects.

What is the recommended strategy for maintaining consistent retrieval speeds as the offset grows? At what record count does the memory overhead of the JS bridge typically trigger performance degradation?