I am indexing millions of nodes. I have core Search and ApacheSolr jacked up to maximum (500 and 200 nodes per cron run respectively) and SuperCron tells me that the core search module takes about 70 seconds to run, but ApacheSolr only 0.25 seconds.

Can I safely increase the ApacheSolr batches beyond 200? Can I do something extreme, like thousands? How might I go about this?

Comments

pwolanin’s picture

pwolanin commented

Is it your server? Then likely you can go substantially higher with on one minding.

You can set the variable to a higher limit - e.g. thousands (one that doesn't appear in the drop down) by using $conf in settings.php as usual.

See the code or README for variable names.

pwolanin’s picture

pwolanin commented
Status: Active » Fixed
janusman’s picture

janusman commented

In my case I have a patched version of the module which lets me index up to 1,000 nodes per cron run. It depends on your server's capacity. (My localhost testing instance on Windows can't go beyond 200, but our production server can handle 1,000 just fine). =)

Todd Young’s picture

Todd Young commented

Yes, it's my server, and that was precisely what I was looking for. Thanks, guys!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.