# Query much faster against timestamp in seconds than milliseconds

**URL:** <https://discuss.elastic.co/t/query-much-faster-against-timestamp-in-seconds-than-milliseconds/58767>\
**Category:** Elasticsearch\
**Created:** [August 24, 2016, 6:05am UTC](https://discuss.elastic.co/t/query-much-faster-against-timestamp-in-seconds-than-milliseconds/58767 "2016-08-24T06:05:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [August 24, 2016, 1:08pm UTC](https://discuss.elastic.co/t/query-much-faster-against-timestamp-in-seconds-than-milliseconds/58767/2 "2016-08-24T13:08:50Z")

</div>

Hi @pricj004,

both fields get stored as `long` internally but `timestampMilliseconds` contains 1,000 times more distinct values than `timestampSeconds` and that's where the difference comes from.

Daniel

---

_[View the full topic](https://discuss.elastic.co/t/query-much-faster-against-timestamp-in-seconds-than-milliseconds/58767)._