|> range(start: v.timeRangeStart, stop:v.timeRangeStop)
|> filter(fn: (r) =>
r.\_measurement == “plc” and
(r.\_field == “T_Wr_prct_TK” or
r.\_field == “Wr_lt_TkN2” or
r.\_field == “Wr_lt_TkN2pneu” or
r.\_field == “Wr_lt_N2LIN”) and
r.host =\~ /${Station:raw}/
)
|> aggregateWindow(every: $\__interval, fn: last, createEmpty: false)
|> drop(columns: \[“day”, “week”, “month”, “year”, “\_stop”, “\_start”\])
|> sort(columns:\[“\_time”\])
This is across multiple different instances of Edge. Ran inPrivate mode and turned on and off all settings.
I reduced max Datapoints to 25k which somewhat fixed the issue but still a noticable difference between Edge and FireFox persists. Anyone can point me in a direction to adress this?
That’s a lot. In theory you will need 250k px display for this case. Good query should return 100-500 datapoints per time series. Check datasource query response size in browser console + number of returned datapoints in the query inspector in each browser.
Usually starts throthling at around 30k data points. This case is around 100k data points. Size is about 7Mb. I agree just reducing data points and optimizing query will solve this issue. Mostly Curious why Edge starts Throttling so hard while FireFox keeps working properly up till 300k data points +
