So, I have the main indexedDB object with about 30,000 entries on which I have to run full-text search queries. By doing this using the ydn fts plugin, a second storage object is created with about 300,000 entries. Now, since the creation of this "index" of the data warehouse takes a lot of time, I realized that it would be faster to distribute the contents of the index. This, in turn, created a zip file of about 7 MB, which after unpacking on the client side yields more than 40 MB of data. I am currently sorting through this data, inserting it one by one (async, so the callback time is used to parse the next lines), which takes about 20 minutes. Since I am doing this against the background of my application through a web artist, this is not entirely unacceptable, but still seems extremely inefficient. After that,as it was populated, the database is actually fast enough to even be used on medium and high level mobile devices, but the time from 20 minutes to one hour on mobile devices is just crazy. Any suggestions on how this could be improved? Or is this the only option that minimizes the number of records? (which would mean writing my own full-text search ... not what I would look forward to)what I would look forward to)what I would look forward to)
source
share