Hi, I'm indexing a 120G data set concurrently. Indexing completes reasonably well when my DRAM size is big enough, like 32G, where the page cache has enough space. But if I decrease my DRAM size to about 2G, for example, the performance significantly drops -- which I expect since the memory available for the page cache is reduced significantly. However, I also see that the hot function now is queue_spin_lock_slowpath which takes more than 50% of cpu cycles.
Could someone please explain why I see a queue_spin_lock_slowpath and what caused it? Thanks,
