Hi. Thanks; we decided to create an index on @ID; QUERY.INDEX works very fast.
On Saturday, 15 August 2020 at 00:32:34 UTC+2 cliff...@gmail.com wrote: > JBase indexes are very stable. We have about 145 throughout all of our > tables. > > > > On Friday, July 31, 2020 at 11:15:36 AM UTC-4, VK wrote: >> >> Hi coleagues. >> >> What is the fastest way to SELECT a set of records from a J4 table: >> >> @IDs are in the format: (account_number)-(date_in_internal_format), e.g. >> 5001-18628. >> >> trying: >> >> SELECT THE.TABLE WITH @ID BETWEEN "5001-18628" "5001-23012" >> >> Result is bit more than a second (Windows 2019 server, enough memory and >> CPUs). Maybe it can be improved? >> >> usr: 1.11 sys: 0.00 elapsed: 0m1.11s >> >> Usage of "GE ... LE" didn't help: >> >> usr: 1.36 sys: 0.00 elapsed: 0m1.36s >> >> Records number: circa 340,000. >> >> Resizing didn't help. >> >> Conversion to JR, as expected, made things a bit worse. >> >> Thought about year-based distribution but haven't given it a try yet. >> >> Last question - is jBASE indexing stable enough to be trusted? >> >> TAFC 13 (no, question isn't about T24!) >> >> -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to jBASE@googlegroups.com To unsubscribe, send email to jbase-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to jbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jbase/1bd350b0-463d-4e12-8d8c-e1080f2beb8dn%40googlegroups.com.
