Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-13692

Solr is very slow with term vectors. Takes 55 seconds for 1000000 records.

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Invalid
    • None
    • None
    • None
    • Environment - Ubuntu 14.04

      Solr 6.6.0

      java 1.8

    Description

      Hi
       
      I made my custom qparser plugin in Solr - 6.6.0 for scoring. The plugin only does cosine similarity of vectors for each record. I use term vectors here. Results are fine!
       
      BUT, Solr response is very slow with term vectors. It takes around 55 seconds for each request for 1000000 records.
      How do I make it faster to get my results in ms ?
      Please respond soon as its lil urgent.
       
      Note: All my values are stored and indexed. I am not using Solr Cloud.
       

      Attachments

        Activity

          erickerickson Erick Erickson added a comment -

          The JIRA issue tracker is not a support portal. Please raise this question on the user's list at solr-user@lucene.apache.org, see: (http://lucene.apache.org/solr/community.html#mailing-lists-irc) there are a lot more people watching that list who may be able to help and you'll probably get responses much more quickly.

          If it's determined that this really is a code issue or enhancement to Solr and not a configuration/usage problem, we can raise a new JIRA or reopen this one.

          In this case, my first guess is that your custom scoring code is the root cause, so you should include what you think the most relevant parts of that code when you move this conversation over to the user's list.

          erickerickson Erick Erickson added a comment - The JIRA issue tracker is not a support portal. Please raise this question on the user's list at solr-user@lucene.apache.org, see: ( http://lucene.apache.org/solr/community.html#mailing-lists-irc ) there are a lot more people watching that list who may be able to help and you'll probably get responses much more quickly. If it's determined that this really is a code issue or enhancement to Solr and not a configuration/usage problem, we can raise a new JIRA or reopen this one. In this case, my first guess is that your custom scoring code is the root cause, so you should include what you think the most relevant parts of that code when you move this conversation over to the user's list.

          People

            Unassigned Unassigned
            saiv Sai Vignan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: