Many thanks, that's good to know, will move to doing that.
On 3 July 2018 at 05:29, Kunal Khatua wrote:
> Yes. The reason you see the sluggishness is because the embedded webserver
> within the Drillbit also acts as a proxy client, which receives the entire
> result set, before converting it
Yes. The reason you see the sluggishness is because the embedded webserver
within the Drillbit also acts as a proxy client, which receives the entire
result set, before converting it into a JSON response for your browser.
This can lead to rather high memory requirements.
I'd recommend using
Yup, running the query through the web UI. If I avoid doing that, would the
UI be more responsive?
Drillbit settings are:
DRILL_HEAP=8G
DRILL_MAX_DIRECT_MEMORY=16G
DRILLBIT_CODE_CACHE_SIZE=2G
The query itself uses a peak of ~3.5Gb memory while it's running.
On 30 June 2018 at 08:18, Kunal
Are you running the query through the WebUI? What are the memory settings of
your Drillbit?
On 6/26/2018 7:45:30 AM, Dave Challis wrote:
Are there any recommended Drill settings to configure in order to ensure
that the web console (running on 8047) remains responsive even under heavy
load?
