【问题标题】:Solr 4.6.0 DataImportHandler speed up performanceSolr 4.6.0 DataImportHandler 加速性能
【发布时间】:2014-02-17 23:13:01
【问题描述】:

我正在使用 Solr 4.6.0,一次索引大约 10'000 个元素,我的导入性能很差。这意味着导入这 10,000 个文档大约需要 10 分钟。我当然知道,这几乎不取决于服务器硬件,但我仍然想知道,如何提高性能以及哪些在现实世界中真正有用情况(加入等)?我也非常感谢精确的示例,而不仅仅是指向官方文档的链接。

这里是data-config.xml

<dataConfig>
    <dataSource name="mysql" type="JdbcDataSource" 
        driver="com.mysql.jdbc.Driver" 
        url="jdbc:mysql://xxxx" 
        batchSize="-1" 
        user="xxxx" password="xxxx" />
    <document name="publications">
        <entity name="publication" transformer="RegexTransformer" pk="id" query="
            SELECT 
                sm_publications.id AS p_id, 
                CONCAT(sm_publications.title, ' ', sm_publications.abstract) AS p_text,
                sm_publications.year AS p_year,
                sm_publications.doi AS p_doi,
                sm_conferences.full_name AS c_fullname,
                sm_journals.full_name AS j_fullname,
                GROUP_CONCAT(DISTINCT sm_query_publications.query_id SEPARATOR '_-_-_-_-_') AS q_id
            FROM sm_publications 
            LEFT JOIN sm_conferences ON sm_conferences.id = sm_publications.conference_id 
            LEFT JOIN sm_journals ON sm_journals.id = sm_publications.journal_id 
            INNER JOIN sm_query_publications ON sm_query_publications.publication_id = sm_publications.id 
            WHERE '${dataimporter.request.clean}' != 'false' OR 
                sm_publications.modified > '${dataimporter.last_index_time}' GROUP BY sm_publications.id">
            <field column="p_id" name="id" />
            <field column="p_text" name="text" />
            <field column="p_text" name="text_tv" />
            <field column="p_year" name="year" />
            <field column="p_doi" name="doi" />
            <field column="c_fullname" name="conference" />
            <field column="j_fullname" name="journal" />
            <field column="q_id" name="queries" splitBy="_-_-_-_-_" />

            <entity name="publication_authors" query="
                SELECT 
                    CONCAT(
                        IF(sm_authors.first_name != '',sm_authors.first_name,''), 
                        IF(sm_authors.middle_name != '',CONCAT(' ',sm_authors.middle_name),''), 
                        IF(sm_authors.last_name != '',CONCAT(' ',sm_authors.last_name),'')
                    ) AS a_name, 
                    sm_affiliations.display_name AS aa_display_name, 
                    CONCAT(sm_affiliations.latitude, ',', sm_affiliations.longitude) AS aa_geo, 
                    sm_affiliations.country_name AS aa_country_name
                FROM sm_publication_authors 
                INNER JOIN sm_authors ON sm_authors.id = sm_publication_authors.author_id 
                LEFT JOIN sm_affiliations ON sm_affiliations.id = sm_authors.affiliation_id 
                WHERE sm_publication_authors.publication_id = '${publication.p_id}'">
                    <field column="a_name" name="authors" />
                    <field column="aa_display_name" name="affiliations" />
                    <field column="aa_geo" name="geo" />
                    <field column="aa_country_name" name="countries" />
            </entity>

            <entity name="publication_keywords" query="
                SELECT sm_keywords.name FROM sm_publication_keywords 
                INNER JOIN sm_keywords ON sm_keywords.id = sm_publication_keywords.keyword_id
                WHERE sm_publication_keywords.publication_id = '${publication.p_id}'">
                    <field column="name" name="keywords" />
            </entity>

        </entity>
    </document>
</dataConfig>

【问题讨论】:

  • 根据我的(有偏见的)经验,查询“SELECT sm_keywords.name FROM sm_publication_keywords INNER JOIN sm_keywords ON sm_keywords.id = sm_publication_keywords.keyword_id WHERE sm_publication_keywords.publication_id = '${publication.p_id}”在每个 p_id 上执行,这很可能是瓶颈。如果可以的话,也许值得尝试将此查询合并到顶级查询中,或者缓存查询结果而不是逐个查询 p_id。
  • 我实际上已经尝试将所有查询合并到主查询中,但最终我得到了重复的条目 (stackoverflow.com/questions/21452199/…)。您能否提供一个查询缓存的精确示例?因为我也尝试了CachedSqlEntityProcessor,但它以ClassCastException 或之后的结果结束,它只是没有以正确的方式合并数据(stackoverflow.com/questions/21549011/…)。

标签: mysql performance solr dataimporthandler


【解决方案1】:

通过查询缓存,我的意思是 CachedSqlEntityProcessor。我喜欢 merged 解决方案,就像您的其他问题 MySQL GROUP_CONCAT duplicate entries 一样。但是 CachedSqlEntityProcessor 也会有所帮助,如果 p_id 在主查询 publication_authors 的结果集中一遍又一遍地重复,并且您不必担心额外的内存使用。

更新:看起来你已经解决了另外两个问题,也许你可以选择任何一种方式,无论如何我都会按照你的要求发布简短的示例/指针,以防其他人发现它很方便

<entity name="x" query="select * from x">
    <entity name="y" query="select * from y" processor="CachedSqlEntityProcessor"  where="xid=x.id">
    </entity>
<entity>

这个例子取自wiki。这仍然会从主查询“select * from x”中运行每个查询“select * from y where xid=id”。但它不会重复发送相同的查询。

【讨论】:

    猜你喜欢
    • 2013-01-27
    • 2012-06-21
    • 2011-10-19
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2013-09-10
    • 2011-08-23
    • 1970-01-01
    相关资源
    最近更新 更多