# What is bad of using pulsing postings format? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 14, 2014, 2:20am UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637 "2014-07-14T02:20:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![11153](https://avatars.discourse-cdn.com/v4/letter/1/e274bd/32.png) [@11153](https://discuss.elastic.co/u/11153)\ **Post date:** [July 14, 2014, 2:20am UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637/1 "2014-07-14T02:20:20Z")
From this article ([http://blog.mikemccandless.com/2010/06/lucenes-pulsingcodec-on-primary-key.html](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? 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Robert\_Muir\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robert_muir_2/32/931_2.png) [@Robert\_Muir\_2](https://discuss.elastic.co/u/Robert_Muir_2)\ **Post date:** [July 14, 2014, 2:41am UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637/2 "2014-07-14T02:41:33Z")
There is not really an advantage to it. The optimization has been incorporated into the default index format of lucene: [[LUCENE-4498] pulse docfreq=1 DOCS\_ONLY for 4.1 codec - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-4498) On Sun, Jul 13, 2014 at 10:20 PM, 陳智清 [walker0902@gmail.com](mailto:walker0902@gmail.com) wrote: > From this article > ([Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields](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? > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B\_yrfS797vgCuADdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B_yrfS797vgCuADdBg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [July 14, 2014, 3:17am UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637/3 "2014-07-14T03:17:08Z")
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](mailto:robert.muir@elasticsearch.com) wrote: > There is not really an advantage to it. > > The optimization has been incorporated into the default index format > of lucene: [[LUCENE-4498] pulse docfreq=1 DOCS\_ONLY for 4.1 codec - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-4498) > > On Sun, Jul 13, 2014 at 10:20 PM, 陳智清 [walker0902@gmail.com](mailto:walker0902@gmail.com) wrote: > > > From this article > > ( > > [Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields](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? > > > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com) > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B\_yrfS797vgCuADdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B_yrfS797vgCuADdBg%40mail.gmail.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3u-moKntRgxuUsD5x3rLpND%3DwFrttULA8CWcy2UTP%3Duw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3u-moKntRgxuUsD5x3rLpND%3DwFrttULA8CWcy2UTP%3Duw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![David\_Smith\_2](https://avatars.discourse-cdn.com/v4/letter/d/a9a28c/32.png) [@David\_Smith\_2](https://discuss.elastic.co/u/David_Smith_2)\ **Post date:** [July 14, 2014, 6:32pm UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637/4 "2014-07-14T18:32:12Z")
+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](mailto: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](mailto:robert.muir@elasticsearch.com) wrote: > > There is not really an advantage to it. > > > > The optimization has been incorporated into the default index format > > of lucene: [[LUCENE-4498] pulse docfreq=1 DOCS\_ONLY for 4.1 codec - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-4498) > > > > On Sun, Jul 13, 2014 at 10:20 PM, 陳智清 [walker0902@gmail.com](mailto:walker0902@gmail.com) wrote: > > > > > From this article > > > ([Changing Bits: Lucene's PulsingCodec on "Primary Key" Fields](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? > > > > > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d4c5ad8-baab-4c81-85a5-dc75095a7f5a%40googlegroups.com). > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B\_yrfS797vgCuADdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMUKNZXKEDQiBw%3DwmyLPh47bkJh%3DUT5E%2B_yrfS797vgCuADdBg%40mail.gmail.com). > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3u-moKntRgxuUsD5x3rLpND%3DwFrttULA8CWcy2UTP%3Duw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3u-moKntRgxuUsD5x3rLpND%3DwFrttULA8CWcy2UTP%3Duw%40mail.gmail.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/828C16E1-6E9B-493E-B9FD-985531747D2D%40gmail.com](https://groups.google.com/d/msgid/elasticsearch/828C16E1-6E9B-493E-B9FD-985531747D2D%40gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:15am UTC](https://discuss.elastic.co/t/what-is-bad-of-using-pulsing-postings-format/18637/5 "2017-07-06T01:15:53Z")