RE: LTR feature extraction performance issues

2017-10-31 Thread Brian Yee
/ LONDON) [mailto:cpoersc...@bloomberg.net] Sent: Tuesday, October 31, 2017 8:48 AM To: solr-user@lucene.apache.org Subject: RE: LTR feature extraction performance issues Hi Brian, I just tried to explore the scenario you describe with the techproducts example and am able to see what you see: # step 1

RE: LTR feature extraction performance issues

2017-10-31 Thread Christine Poerschke (BLOOMBERG/ LONDON)
-user@lucene.apache.org Subject: RE: LTR feature extraction performance issues Hi Alessandro, Unfortunately some of my most important features are query dependent. I think I found an issue though. I don't think my features are being inserted into the cache. Notice "cumulative_inserts:0&q

RE: LTR feature extraction performance issues

2017-10-30 Thread Brian Yee
:01 AM To: solr-user@lucene.apache.org Subject: Re: LTR feature extraction performance issues It strictly depends on the kind of features you are using. At the moment there is just one cache for all the features. This means that even if you have 1 query dependent feature and 100 document dependent featur

RE: LTR feature extraction performance issues

2017-10-24 Thread Brian Yee
ubject: Re: LTR feature extraction performance issues It strictly depends on the kind of features you are using. At the moment there is just one cache for all the features. This means that even if you have 1 query dependent feature and 100 document dependent feature, a different value for the quer

Re: LTR feature extraction performance issues

2017-10-23 Thread alessandro.benedetti
It strictly depends on the kind of features you are using. At the moment there is just one cache for all the features. This means that even if you have 1 query dependent feature and 100 document dependent feature, a different value for the query dependent one will invalidate the cache entry for the

LTR feature extraction performance issues

2017-10-20 Thread Brian Yee
I enabled LTR feature extraction and response times spiked. I suppose that was to be expected, but are there any tips regarding performance? I have the feature values cache set up as described in the docs: Do I simply have to wait for the cache to fill up and hope that response times go down?