Slow degradation of index about paradedb HOT 6 OPEN

Thanks for reporting this. To make sure I understand, you're seeing this slowdown after a few thousand writes to the index.

Could you clarify that means a few thousand separate transactions, each with around one row being updated?

from paradedb.

Thanks for reporting this. To make sure I understand, you're seeing this slowdown after a few thousand writes to the index.

Could you clarify that means a few thousand separate transactions, each with around one row being updated?

exactly, it is thousands of separate updates and inserts into the indexed column, very often those updates are with the exactly same data (its just how the SW works, it updates columns even if they didnt change).

I let it run for last few hours just now... doing updates on data without really changing the data and it still got the slow down - so maybe that might be some clue? not sure...

from paradedb.

Hello, are you able to replicate this bug or should i prepare exact step by step to replicate it? I might have some time this weekend to do it if needed

from paradedb.

Hello, are you able to replicate this bug or should i prepare exact step by step to replicate it? I might have some time this weekend to do it if needed

If you have exact steps to replicate it would be extremely helpful. We haven't managed to replicate just yet

from paradedb.

I just tried to do vaccuum full, when the degradation occured and it completely fixed the issue... so I am not sure if it is a bug or just feature, it happens quite fast (only one thousand inserts/updates) and the degradation is quite big (like 10x slower queries)... So I guess I will still prepare the step by step so you can see for yourself, never happened to me before with any other indexes that the slow down would be so fast and so big, so maybe it should be checked anyway.

from paradedb.