# Search and Index updates in parallel **URL:** \ **Category:** Elasticsearch\ **Created:** [December 12, 2013, 7:53pm UTC](https://discuss.elastic.co/t/search-and-index-updates-in-parallel/14842 "2013-12-12T19:53:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Bijuv\_V](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@Bijuv\_V](https://discuss.elastic.co/u/Bijuv_V)\ **Post date:** [December 12, 2013, 7:53pm UTC](https://discuss.elastic.co/t/search-and-index-updates-in-parallel/14842/1 "2013-12-12T19:53:12Z")
Hi, I want to update the elastic search index very frequently as the data that is indexed is volatile. So my question is , when the index is getting updated, will the search query that is happening on the same index have an impact on the performance? If there is no impact on the performance, how does Elastic Search achieve the same? If this is already documented, a pointer to the documentation will also help. 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/CALU-2jzwnj4m0f6X%3DAtUrim7jzMWvN6KC2Ak2QuHe21fGfn3HA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALU-2jzwnj4m0f6X%3DAtUrim7jzMWvN6KC2Ak2QuHe21fGfn3HA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [December 12, 2013, 8:21pm UTC](https://discuss.elastic.co/t/search-and-index-updates-in-parallel/14842/2 "2013-12-12T20:21:22Z")
Updates followed by queries on fields will lag a bit, depending on the default index interval. But a get-by-id will be realtime. For example, I wrote a performance test case in which I created a custom mapping with no indexing on the fields. My driver had one or more writer threads that created unique \_id values and added documents to the index + type + \_id. The writers then passed the \_id values onto one or more reader threads that queried based on index + type + \_id. Also, all of the documents in the index + type were given a 10s time to live, and the default TTL processing was left at 60s. (This meant that expired documents would remain for up to about 50s). No errors were seen; no update failures, and no query failures. ES and its use of the JVM were solid, showing steady and sustainable throughput. On a quad-core i7 MacBook Pro laptop (disk spindles, not SSD), I could sustain a throughput of about 5000 documents created, added, and queried per second. This also included serialization to and from JSON. I used the Jackson 2 libraries and Jackson data binding to do the serialization. (ES provides only the streaming API of Jackson 1.9. It would seem a good update for ES 1.0 to include the full (3 jars worth) of Jackson 2. But if not, then the jars are easy to add, as ES nicely re-packages all of its internal dependent jars to avoid conflicts: jackson-annotations-2.2.3.jar jackson-core-2.2.3.jar jackson-databind-2.2.3.jar Hope this helps. It's not a typical use case, but one of the several important ones to me. Regards, Brian -- 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/c4455406-8873-47a2-b160-0b1508aac272%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c4455406-8873-47a2-b160-0b1508aac272%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:01am UTC](https://discuss.elastic.co/t/search-and-index-updates-in-parallel/14842/3 "2017-07-06T02:01:37Z")