MSVBASE HNSW Index Construction Is Very Slow and Appears Single-Threaded

[lmccccc]

I notice that MSVBASE HNSW index construction is very slow.

While building the index, I monitored the system using top and PostgreSQL PIDs from Docker. CPU usage stays around one core, and only one backend process is active. This suggests the HNSW index is constructed in a single thread.

This happens even though I configured the worker pool to 64.

Question:
Is MSVBASE HNSW index construction single-threaded by design?
If yes, are there any plans or configs to enable multi-threaded / parallel index build?

Thanks.