Hi Robert, current Solr compression will work really well , both for Stored and DocValues contents. Related the index term dictionaries, I ask for some help to other experts as I never checked how the actual compression works in there, but I assume it is quite efficient.
Usually the field type affects performance both for specific features and functions, for example if you are interested in range queries on Integers, you should try the trieInt implementation. Let us know for more details ! Cheers On 16 October 2015 at 07:53, Robert Krüger <krue...@lesspain.de> wrote: > Hi, > > I have a data model where I would store and index a lot of integer values > with a very restricted range (e.g. 0-255), so theoretically the 32 bits of > Solr's integer fields are complete overkill. I want to be able to to things > like vector distance calculations on those fields. Should I worry about the > "wasted" bits or will Solr compress/organize the index in a way that > compensates for this if there are only 256 (or even fewer) distinct values? > > Any recommendations on how my fields should be defined to make things like > numeric functions work as fast as technically possible? > > Thanks in advance, > > Robert > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
