From this article
(http://blog.mikemccandless.com/2010/06/lucenes-pulsingcodec-on-primary-key.html)
I know pulsing codec saves one disk seek hence introduces performance gain.
I would like to know what I pay for using pulsing codec? What will happen
if I give it a high cut-off frequency so that all postings are stored in
term dictionary?
In other words, instead of the goodness, I would like to know what is the
drawback of using pulsing postings format?
From this article
(Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields)
I know pulsing codec saves one disk seek hence introduces performance gain.
I would like to know what I pay for using pulsing codec? What will happen if
I give it a high cut-off frequency so that all postings are stored in term
dictionary?
In other words, instead of the goodness, I would like to know what is the
drawback of using pulsing postings format?
If it doesn't have an advantage can it be deprecated? The whole codecs
page of the Elasticsearch guide seems like it could use a once over by
someone that really knows what they are doing. I.E. not me
On Jul 13, 2014 10:41 PM, "Robert Muir" robert.muir@elasticsearch.com
wrote:
From this article
( Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields
)
I know pulsing codec saves one disk seek hence introduces performance
gain.
I would like to know what I pay for using pulsing codec? What will
happen if
I give it a high cut-off frequency so that all postings are stored in
term
dictionary?
In other words, instead of the goodness, I would like to know what is the
drawback of using pulsing postings format?
Thank you.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
+1 on having more information on codecs/postings format. Including examples on where each makes sense and where they don't.
The current documentation on the codec module page in reference doesn't make the trade offs very clear. It's quite vague to somebody who has not used it (not complaining just a statement FYI) before. I think having examples where each makes sense and where they don't would make things much clearer.
Thank you.
On Jul 13, 2014, at 11:17 PM, Nikolas Everett nik9000@gmail.com wrote:
If it doesn't have an advantage can it be deprecated? The whole codecs page of the Elasticsearch guide seems like it could use a once over by someone that really knows what they are doing. I.E. not me
On Jul 13, 2014 10:41 PM, "Robert Muir" robert.muir@elasticsearch.com wrote:
There is not really an advantage to it.
From this article
(Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields)
I know pulsing codec saves one disk seek hence introduces performance gain.
I would like to know what I pay for using pulsing codec? What will happen if
I give it a high cut-off frequency so that all postings are stored in term
dictionary?
In other words, instead of the goodness, I would like to know what is the
drawback of using pulsing postings format?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
