This message was deleted.
# troubleshooting
s
This message was deleted.
c
we switched to using roaring bitmaps for indexes by default in druid 0.18, it could be related to that if you have lots of super high cardinality columns
👍 1
performance is like a ton better with roaring though so the size is probably worth it unless you were never filtering by those columns
d
yeah, roaring bitmap is definitely preferable. I don’t want to switch it off
c
actually if you’re never filtering on the column, the better option is to not write indexes for it, there is a flag on dimension schema to control
d
yes, that is what we usually do
c
👍
d
Another related question, could imperfect rollup impacted the smoosh file?
c
yeah totally
also column order can play a pretty big role
if you’re on the latest version of druid and feeling adventurous and looking to make segments smaller, i did a thing that seems pretty cool in tests so far that added an option at ingest time to make the strings stored in segments smaller, particularly if they have lots of shared prefixes, such as urls
its not really backwards compatible, so only make segments like that if you don’t need to read them on any older versions of druid
also definitely experiment with your workload to ensure there are no performance regressions that i’ve missed before using in production
d
ah… thank you for your information!