Per the current API, orderQueue() is suppose to re-index?

Sam wrote:

George wrote:I will add a reindexQueue method, this should be something which doesn't lag things.

I was playing with some group API code and noticed that changing priorities within a group didn't lag (~100 items, lag ~5-10 secs) like changing priorities within the total torrent list (~1300 items, lag ~2 mins). I'll guess that reindexing the group is only doing 100 writes to disk and the reindex for the total torrent list is doing 1300 writes, hence the extreme increase in lag times? That doesn't really make logical sense, but it seemed the observed pattern.

The reason I bring this up is, what are your thoughts on excluding all non-queued torrents from the QM completely?

On my system that would eliminate 600+ writes per QM update.

Best,
Sam

Edit:
I should have more extensively played with KT4 before writing the above. Lags seems negligible now, and my primary reference point (moving a torrent manually in the QM) lags within the one second range (from 2-4 minute range). Please close all Lag issues I've brought up, as you've seemed to have solved them.

Thank you George,
Sam