Closed OmgImAlexis closed 9 years ago
I'm pretty sure this is just due to mongodb indexing. Indexing is necessary to have search queries run in under a couple seconds instead of 2-3 minutes (Yes, it actually took that long before I enabled indexing.)
I don't think there's much that can be done. At the beginning mongodb doesn't have much indexing work to do, but it's probably piling up as it goes along.
That's fine, just thought I'd report it incase there was an easy fix. Shall I close this?
I tried importing E002 from bitsnoop, it imported the first 1,347,223 fine at a rate of 1,000 - 5,000 a second but torrents after that loaded extremely slow at a rate of about 100 a second. I've using a Macbook Pro 2010 with 8GB RAM and a 265GB SSD, I also had about 4GB of free RAM and over 100GB of free disk space so I don't think I was hitting any IO limits.