Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dbaldacchino opened this issue Dec 17, 2018 · 1 comment
Open

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

dbaldacchino opened this issue Dec 17, 2018 · 1 comment
Assignees

Comments

@dbaldacchino
Copy link

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. "

@djsiroky djsiroky self-assigned this Dec 17, 2018
@djsiroky djsiroky transferred this issue from another repository Dec 17, 2018
@djsiroky
Copy link
Member

Working in this in zombie-logs-datatable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants