Question on caching/ filtering performance issues with server side processing

Question on caching/ filtering performance issues with server side processing

swetha_pendyswetha_pendy Posts: 41Questions: 3Answers: 0

Implemented server side processing with Python Flask, which gives page loading results under 15 seconds for 32k+ rows of data. Every new request is being sent to server and it takes 15 seconds when clicked on Page 2, 3 etc. Also, when the individual column filtering is performed, this is also being sent to server side and taking 15 seconds to five the filtered results. Can you please suggest as to how the filtering results can be provided quickly ? Are there any suggestions if the approach can be different ? I understand the performance improvement has been drastically reduced from 4 minutes to 15 seconds on initial page loading but clicking on each page and filtering is taking 15 seconds each which is annoying. Can you please suggest?

Replies

  • kthorngrenkthorngren Posts: 21,343Questions: 26Answers: 4,954

    I'm assuming your Flask application supports the Server Side processing protocol and only returns the rows for the page. For example if the page length is 10 then only 10 rows of data are returned to the client for each request.

    Likely the delay is on the server side in fetching the data as it should take long for Datatables to render a page of data. There could also be network delay between the client and the server.

    Let us know what you find.

    Kevin

Sign In or Register to comment.