This message was deleted.
# troubleshooting
s
This message was deleted.
s
I see that for my queries, the query/segment/time takes the most time on the historical. What generally causes query segment time spikes and how can it be brought down?
j
High segment scan time could be due to scanning the bulk of the data in the segment. Are these queries "heavy" group by queries that do not have highly selective filters on them? Is there a high wait time as well?
s
Yeah most of the queries don't have filters on them, but the total datasource size isn't large (~150GB) Is there a way to improve the speed of these queries? Would increasing the heap help? We have heap set to 10g currently
f
are you using Druid 25?
s
Wait time is negligible. Almost all of the query time is spent on query segment time
Yes I'm using 25
f
there’s no easy answer to ‘why are queries slow’ - it can be because the data model is incorrect, the query itself is written in an inefficient way, there’s insufficient hardware, etc
can you post the query you are trying to run and details about your cluster?
v
You can also book a time in the POC clinic https://calendly.com/druidcommunity/clinic-poc