Masajiro Iwasaki

It seems that `qbg build-qg` didn't generate the quantized graph index. Did `qbg build-qg` complete without any issues excluding `cp error`?

The `build-qg` has three phases, and from the messages, it looks like the first two phases had completed and the third phase was still in progress. Since your data is...

The third phase consumes a large amount of memory, which might be causing OOM. Reducing the value 128 in the following commands might help the process complete successfully: ``` ......

What I meant in my previous comment was to suggest reducing the number of edges further from 128 — perhaps trying 64, for example.

Just to be safe, trying a smaller value like 16 might be helpful to confirm that it runs correctly.

I estimated the memory usage. ``` 16 edges -> 650 G 64 edges -> 2,400 G 128 edges -> 4,800 G ``` Therefore, it is possible that only the QG...

Hello, These two are basically the same in functionality. First, I created the command-line tool. Later, when I added API functionality and the sample code, I consolidated the functionality of...

Thank you for the information. However, the following message seems strange. `inverted index object size=2408074` The expected value is 113676656, which comes from the file `ivt`. I've updated the source...

As for your questions 1 to 3, the issues might be caused by your dataset. First, I recommend trying the same operation using the NGT command-line tools (ngt and qbg)....

Thank you for the information. Since we couldn’t reproduce the issue on our side, it is difficult to fix it directly. However, we found a few things that looked suspicious...