Correlation store hot spot
Reported by Ben Hood | September 30th, 2011 @ 02:01 PM | in 0.9-series (closed)
There appears to be a hot spot in the LuceneVersionCorrelationStore which is due to the fact that a new IndexSearcher instance is created for each operation. This seems to be quite expensive.
Comments and changes to this ticket
-
Ben Hood September 30th, 2011 @ 03:13 PM
(from [f35942037eee093660bfbc77b01b20c4e20b6a8b]) [#370] Create a searcher from the current writer instance https://github.com/lshift/diffa/commit/f35942037eee093660bfbc77b01b...
-
Ben Hood September 30th, 2011 @ 07:58 PM
- State changed from “new” to “resolved”
- Assigned user changed from “Ben Hood” to “Paul Jones”
I accidentally committed this straight on master and hence it has gone out already, but in deployment, it appears to have made a significant difference, so I'll leave it on master and wait for it to get post-QA'ed.
-
Paul Jones October 13th, 2011 @ 02:13 AM
- State changed from “resolved” to “closed”
Seems like a fairly simple patch, and appears to be working.
=> QA+
-
Ben Hood November 14th, 2011 @ 05:35 PM
- Milestone set to “0.9-series”
- Milestone order changed from “112” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood