# Update write intensive counters performance **URL:** \ **Category:** Elasticsearch\ **Created:** [March 28, 2015, 5:27am UTC](https://discuss.elastic.co/t/update-write-intensive-counters-performance/22955 "2015-03-28T05:27:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Lorne\_Sorn](https://avatars.discourse-cdn.com/v4/letter/l/df788c/32.png) [@Lorne\_Sorn](https://discuss.elastic.co/u/Lorne_Sorn)\ **Post date:** [March 28, 2015, 5:27am UTC](https://discuss.elastic.co/t/update-write-intensive-counters-performance/22955/1 "2015-03-28T05:27:37Z")
Hello, I have a multiple field structure in which i have 2-3 fields with text that will be searchable and besides that i have 3 very write intensive fields (counters) in this structure. Those fields will only need to be visible in results but will not be a part of the search query. How to update those counters in the most efficient way ? So without reindexing anything etc. How to handle them best? What kind of performance (updates per second) we are talking about on updating those counters lets say on one Xeon E3-1230 v3 or any other cpu? Kind regards. -- 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/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 28, 2015, 5:50am UTC](https://discuss.elastic.co/t/update-write-intensive-counters-performance/22955/2 "2015-03-28T05:50:14Z")
Performance is based on your dataset, you'd have to test it yourself. Ideally you want to separate hot and cold data, so that when you do update you don't need to reindex the whole document (which is what an update does in ES). You can do this via parent/child relationships, or having two indices with each part of the doc that you then join them externally, as two examples. On 28 March 2015 at 16:27, Lorne Sorn [dulo65330@gmail.com](mailto:dulo65330@gmail.com) wrote: > Hello, > > I have a multiple field structure in which i have 2-3 fields with text > that will be searchable and besides that i have 3 very write intensive > fields (counters) in this structure. Those fields will only need to be > visible in results but will not be a part of the search query. How to > update those counters in the most efficient way ? So without reindexing > anything etc. How to handle them best? What kind of performance (updates > per second) we are talking about on updating those counters lets say on one > Xeon E3-1230 v3 or any other cpu? > > Kind regards. > > -- > 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/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com?utm_medium=email&utm_source=footer) > . > 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/CAEYi1X\_Rfyv\_q%3D1b5gdgx0xLNJJE%3DysJibi8cYY7ZttXYWWNxw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_Rfyv_q%3D1b5gdgx0xLNJJE%3DysJibi8cYY7ZttXYWWNxw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Lorne\_Sorn](https://avatars.discourse-cdn.com/v4/letter/l/df788c/32.png) [@Lorne\_Sorn](https://discuss.elastic.co/u/Lorne_Sorn)\ **Post date:** [March 28, 2015, 6:14am UTC](https://discuss.elastic.co/t/update-write-intensive-counters-performance/22955/3 "2015-03-28T06:14:50Z")
Thanks for replying. So basically by making those 3 int counters inside child i will only reindex those 3 ints yes ? Dataset for now is around 50k documents. Then what's the performance of only reindexing 2-3 ints on lets say performance of Xeon E3-1230 v3 or any E5 or i7 etc or any other cpu. I would like an estimate, just to know if we are talking about ~50k updates per sec or ~10k or ~1k depending on cpu. Just an estimate would be really helpful. On Saturday, March 28, 2015 at 6:50:45 AM UTC+1, Mark Walkom wrote: > Performance is based on your dataset, you'd have to test it yourself. > > Ideally you want to separate hot and cold data, so that when you do update > you don't need to reindex the whole document (which is what an update does > in ES). > You can do this via parent/child relationships, or having two indices with > each part of the doc that you then join them externally, as two examples. > > On 28 March 2015 at 16:27, Lorne Sorn \<[dulo...@gmail.com](mailto:dulo...@gmail.com) \\> > wrote: > > > Hello, > > > > I have a multiple field structure in which i have 2-3 fields with text > > that will be searchable and besides that i have 3 very write intensive > > fields (counters) in this structure. Those fields will only need to be > > visible in results but will not be a part of the search query. How to > > update those counters in the most efficient way ? So without reindexing > > anything etc. How to handle them best? What kind of performance (updates > > per second) we are talking about on updating those counters lets say on one > > Xeon E3-1230 v3 or any other cpu? > > > > Kind regards. > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/49b59206-3c01-440e-8553-4a3b367296df%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > 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/8d2f72ed-0311-4bf1-8f55-5be3110f0884%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8d2f72ed-0311-4bf1-8f55-5be3110f0884%40googlegroups.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, 12:23am UTC](https://discuss.elastic.co/t/update-write-intensive-counters-performance/22955/4 "2017-07-06T00:23:19Z")