# Would replacing millisecond with seconds still help query faster?

**URL:** <https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115>\
**Category:** Elasticsearch\
**Created:** [June 15, 2018, 4:09pm UTC](https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115 "2018-06-15T16:09:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kennethnanwu](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@kennethnanwu](https://discuss.elastic.co/u/kennethnanwu)\
**Post date:** [June 15, 2018, 4:09pm UTC](https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115/1 "2018-06-15T16:09:24Z")

</div>

I was getting lots of timeout errors so I was trying to improve query speed and came across this thread: [Query much faster against timestamp in seconds than milliseconds](https://discuss.elastic.co/t/query-much-faster-against-timestamp-in-seconds-than-milliseconds/58767/2)  
I tried using seconds for timestamp in my environment and it is not helping. it is mentioned in the thread that querying would be based on a tree in the next major release. I believe this "next release" is the version I am using (6.2.4). so I am wondering would replacing millisecond with seconds still help?

---

<div class="post-metadata">

**Author:** ![Lumaraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lumaraf/32/50639_2.png) [@Lumaraf](https://discuss.elastic.co/u/Lumaraf)\
**Post date:** [June 18, 2018, 10:29am UTC](https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115/2 "2018-06-18T10:29:11Z")

</div>

Major improvements were made to how numeric field are handled in elasticsearch 5 and later. I would not expect any relevant performance improvement from changing the precision.

You might be interested in these two articles about numeric field improvements:

> **[Searching numb3rs in 5.0
	  	 | Elastic](https://www.elastic.co/blog/searching-numb3rs-in-5.0)**
>
> Lucene 6.0 introduced new exciting feature called multi-dimensional points. While the name of the feature puts a lot of emphasis on the fact that it supports multiple dimensions, this feature behaves ...

  

> **[Query Planning for Range Queries in Elasticsearch](https://www.elastic.co/blog/better-query-planning-for-range-queries-in-elasticsearch)**
>
> Taking our efforts to make range queries in Elasticsearch faster to a new level and exploring when they're used in conjunctions.

---

<div class="post-metadata">

**Author:** ![kennethnanwu](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@kennethnanwu](https://discuss.elastic.co/u/kennethnanwu)\
**Post date:** [June 18, 2018, 3:50pm UTC](https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115/3 "2018-06-18T15:50:11Z")

</div>

thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 16, 2018, 3:50pm UTC](https://discuss.elastic.co/t/would-replacing-millisecond-with-seconds-still-help-query-faster/136115/4 "2018-07-16T15:50:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.