lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-2356) indexing using DataImportHandler does not use entire CPU capacities
Date Fri, 26 Apr 2013 08:00:21 GMT


Jan Høydahl commented on SOLR-2356:

Put in in example/webapps/dih.war and it would live by default in http://localhost:8983/dih/
- same host, same port...
Now that we have the new schema REST API, it could get the schema from there to validate correct
fields etc.
Using the Collections API, a standalone app could ask user which collection to index a certain
table into.

And it could support automated full reindex without downtime and even with schema change:
1) create a new collection 2) index everything from scratch 3) swap/alias the new using the
old name 4) delete the old collection. More flexible
> indexing using DataImportHandler does not use entire CPU capacities
> -------------------------------------------------------------------
>                 Key: SOLR-2356
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 4.0-ALPHA
>         Environment: intel xeon processor (4 cores), Debian Linux Lenny, OpenJDK 64bits
server v1.6.0
>            Reporter: colby
>            Priority: Minor
>              Labels: test
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> When I use a DataImportHandler to index a large number of documents (~35M), cpu usage
doesn't go over than 100% cpu (i.e. just one core).
> When I configure 4 threads for the <entity> tag, the cpu usage is splitted to 25%
per core but never use 400% of cpu (i.e 100% of the 4 cores)
> I use solr embedded with jetty server.
> Is there a way to tune this feature in order to use all cores and improve indexing performances
> Because for the moment, an extra script (PHP) gives better indexing performances than
> thanks

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message