Skip to content

Crashing when querying large data range (Zombie Logs) #253

@dbaldacchino

Description

@dbaldacchino

Dan: "I'm not sure the root cause, but I do know that searching through such a wide date range is a problem right now. It pull all the data an filters client-side. So your browser probably received 50MB+ for that date range. I can work on moving the processing server-side. After that we can see if that's still an issue for you."

Dave: "Thanks Dan, yeah I should have realized it was going to be a lot of data but I set the date back as I couldn’t find a particular set of records. This isn’t something we/I need to do frequently so please let’s not worry about it too much for now. I can specify a smaller moving window until I find what I need instead of a wide range. Thanks again."

Konrad: "Dan is correct that it would cause issues to ask for such a big range of data. We have been implementing server side processing for all of these tables, and limiting the amount of data returned in order to remedy this. I was pulled off Mission Control for now, so I am not sure if I will be able to get around to this anytime soon. "

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions