Discussing Large JSON File's Latency in Typesense
TLDR Daniel asked about handling a large JSON file in Typesense. Kishore Nallan explained the slowdown is due to wildcard queries hitting and sorting entire records. He suggested enabling caching to improve performance.
Dec 01, 2021 (26 months ago)
Kishore Nallan12:30 PM
Kishore Nallan12:40 PM
*) on 0.22 RC builds (0.22 GA release is right around the corner)
Kishore Nallan12:45 PM
In the mean time, on 0.22 we also have a way for you to enable caching, so you can use that to handle this. Set
use_cache=trueparameter. You can also set a
cache_ttlparameter in seconds (default is 60 seconds) as a scoped API key parameter if you want to cache for longer duration.
Kishore Nallan12:54 PM
Indexed 3015 threads (79% resolved)
Debugging Search Issue with Typesense Server Caching
Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns
Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.
Large JSONL Documents Import Issue & Resolution
Suraj was having trouble loading large JSONL documents into Typesense server. After several discussions and attempts, it was discovered that the issue was due to data quality. Once the team extracted the data again, the upload process worked smoothly.
Issue with Search Duration on Typesense Database
Robert reported an issue about query time delay when adding a `filter_by` constraint in a large Typesense database. Kishore Nallan explained that this happens due to the order of operation and also promised to look into this issue further. Robert withdrew his interest in sponsoring the improvement due to moving from the project.
Slow, High CPU Write Operations After Collection Drop in Typesense
Himank discussed an issue in Typesense where deleting and recreating a collection led to slow write operations and high CPU usage. Kishore Nallan suggested using an alias to avoid this issue. Numerous tests and debugging was conducted as pboros contributed with local testing. Kishore Nallan aimed to start implementing a range delete and full db compaction after deletion to potentially solve the issue.