-
The current logic of indexers is implemented in a sub-optimal (from the performance perspective) fashion: many requests for txes are repeated, significantly increasing validation time for the large wa…
-
Hi, thanks for the great package! Currently I'm trying to build a kNN with custom metrics for DTW, but the index building for just 90k of data would take around 5 hours. Do you have any suggestions to…
-
#418 has shown that the typical steps for a search are:
1. Read the zim file (to be able to locate the xapian index in it) : Cold : 7.44s | Warm : 0.12s
2. Open the xapian database (internal xapian …
-
### Description
I have been looking at many ingestion flame charts recently, in the context of TSDB and merging changes. They highlighted a few things we could do to speed up indexing a bit, so I t…
-
Hi,
I have recently encountered tons of error of speed options in move_chuck_contact and move_chuck_seperation(). But in debug mode, sometimes, it works again without doing any changes.
```
s…
-
### Question Validation
- [X] I have searched both the documentation and discord for an answer.
### Question
Hello!
Thank you for your great project!
I've built a huge vector store index and s…
-
-
```
Async file operations should be used for indexing. Currently they done as
sync, and CPU is not busy.
```
Original issue reported on code.google.com by `erym...@gmail.com` on 17 Dec 2006 at 3:21
-
Archived orders are keyed on order ID, but retrieved chronologically in most cases. For huge DBs, this is prohibitive. We need smarter indexing of those orders to speed things up.
-
Hi,
I was wondering if you have any benchmarks available that demonstrate `jaqt` performance, especially in comparison to lightweight databases like SQLite (when applicable). Since you mentioned that…