# How about the upgrade performance? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 2, 2014, 3:20am UTC](https://discuss.elastic.co/t/how-about-the-upgrade-performance/16753 "2014-04-02T03:20:50Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Meng\_Li](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@Meng\_Li](https://discuss.elastic.co/u/Meng_Li)\ **Post date:** [April 2, 2014, 3:20am UTC](https://discuss.elastic.co/t/how-about-the-upgrade-performance/16753/1 "2014-04-02T03:20:50Z")
Hi, guys: We are a heavy user of es for log searching, one log job is now indexing more than 10,000 lines per minute (just name it as 'A') We now have another log 'B' which we want to join it into A with the \_id , and we decide to use update operation. B is relatively small, 2 million a day and not real-time,( but will go up in the future) Anybody here know the performance of update? Or will the cluster's performance go down facing the frequent update? Both production environment experience and theoretical explanation are appreciated. 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/4cbfb523-9d57-44e6-a9e5-0f577521dab7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4cbfb523-9d57-44e6-a9e5-0f577521dab7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [April 7, 2014, 7:16am UTC](https://discuss.elastic.co/t/how-about-the-upgrade-performance/16753/2 "2014-04-07T07:16:47Z")
Hey, an update operation is nothing else than a reindex operation - which in turn marks the old document as deleted and creates a new document. Also an update operations fetches the document from the index first, and then applies the specified updates from the request. So basically you are just doing two million more get and two million more index operations per day - something that should work, depending of your current cluster is already at its capacity or not. As usual the easiest way is to try it out on your staging/testing systems... --Alex On Wed, Apr 2, 2014 at 5:20 AM, Meng Li [remindme2009@gmail.com](mailto:remindme2009@gmail.com) wrote: > Hi, guys: > > We are a heavy user of es for log searching, one log job is now indexing > more than 10,000 lines per minute (just name it as 'A') > We now have another log 'B' which we want to join it into A with the \_id > , and we decide to use update operation. > B is relatively small, 2 million a day and not real-time,( but will go up > in the future) > Anybody here know the performance of update? Or will the cluster's > performance go down facing the frequent update? > Both production environment experience and theoretical explanation are > appreciated. > 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/4cbfb523-9d57-44e6-a9e5-0f577521dab7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4cbfb523-9d57-44e6-a9e5-0f577521dab7%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/4cbfb523-9d57-44e6-a9e5-0f577521dab7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4cbfb523-9d57-44e6-a9e5-0f577521dab7%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/CAGCwEM-7E11\_%3DfNsGcwwSYwh1%2BbGBWXYO%3DsA4ggNUf0LoSp7UQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM-7E11_%3DfNsGcwwSYwh1%2BbGBWXYO%3DsA4ggNUf0LoSp7UQ%40mail.gmail.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:37am UTC](https://discuss.elastic.co/t/how-about-the-upgrade-performance/16753/3 "2017-07-06T01:37:53Z")