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
Taking too long time on Huge Tables. #1
Comments
Hello @Mvsatish this seems to be a problem of django-filter -- I've opened the carltongibson/django-filter#442 issue there to see if there's a solution. Thanks for noticing this! |
Hello @Mvsatish , finally the issue is resolved! You need to use Best regards, |
@spapas Thanks! This is fantastic. 👍 |
Hey! I have a table with 1.4 Million rows. I used RequestConfig inside my view function, like this to load Data onto DjangoTables2 without filter search:
This method takes almost no time to load the data and pagination also super fast. Now, i want to implement filter search on columns and used your example, which results in consuming total memory (4 GB on dev machine) and yet too long time, sometimes crashing.
Is there a way, i achieve best of both? Speed data loading and filters?
Thanks!
The text was updated successfully, but these errors were encountered: