For one of our clients, we are running a Drupal site with about a millions of nodes. Before launch, those nodes are imported from another database and then indexed into Apache SOLR. The total time to index all of these nodes in an empty SOLR instance is measured in days rather than hours or minutes.
A bit too long to do this import regularly. So me and my (XDebug) profiler delved into the Apache SOLR module code to look where we could scrape of a few hours/days of the execution time.
Seemed like in our case, there were 3 components responsible for a large share of the execution time. Let's have a look.
BTW. We are using the latest dev build of version 2 of the Apache SOLR module.
read more



Recent comments
20 weeks 5 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago
22 weeks 2 days ago