Heh heh. I wasn't asking you to actually USE convert to sqlite memory in your library. I was just saying that for a few xqueries yours a really useful library, but for lots of queries against a large array, the performance of first converting to an sqlite memory database and then querying that and converting back to array would likely be noticibly better performance wise.
I already wrote code and posted it for converting a numbered array to a sqlite memory database so let me know if you didn't get that so you don't have to rewrite it all. Bob S > On Apr 18, 2018, at 15:20 , Alex Tweedly via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Well, it's only a case of "I expect ..." so we shouldn't trust my intuition > until we've benchmarked it a bit :-) > > Having said that - we will still be using script to iterate over the > keys/elements of the array, so there is likely to be some cost there - even > before we allow sqlite to index some columns. > > I've just started looking at it from the performance point of view, and > reduced the time for the simple case in the included test stack by 95% so it > doesn't feel so bad now .... but I'll need to completely rewrite the main > functions/handlers :-( > > I'll try to import the data into an sqlite DB and compare against that too - > will report with some numbers tomorrow (and come up with a more reasonable > test case. > > Alex. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
