# Integer size vs Long size **URL:** \ **Category:** Elasticsearch\ **Created:** [February 14, 2013, 1:25am UTC](https://discuss.elastic.co/t/integer-size-vs-long-size/10736 "2013-02-14T01:25:21Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 14, 2013, 8:45am UTC](https://discuss.elastic.co/t/integer-size-vs-long-size/10736/2 "2013-02-14T08:45:16Z")
Have you disabled \_source and \_all for your test? Note, Lucene is an inverted index, it is not behaving like a bag of documents of primitive data types. In spite there are field types like LongField, IntField, DoubleField, FloatField for numerics, this does not determine the overall size of the index files. To simplify, imagine a list of pointers pointing to longs, and a list of pointers pointing to ints. These posting list elements uses the same memory size, no matter what kind of fields you have in a document. Jörg -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). --- _[View the full topic](https://discuss.elastic.co/t/integer-size-vs-long-size/10736)._