Server side vs client side processing for datatables
Server side vs client side processing for datatables
Hi All,
I would like to know how much data ie7 can handle. I will have around 2000 rows with 4 columns. Shall I go with client side processing. As we know there are lot of benefit you get with this awesome library at client side and response time is very fast.
I can see couple of pros and cons
Server side :
Pros
1) I am using hibernate so there will lot of object going to create if I send all the data in one request which could be avoided if I request minimum data.
2) User will not see stale data cause data will be in sync with server database most of the cases.
cons)
1) I have to code all the features more code means more bug :)
2) There will be lot of request for search feature.
Client Side just opposite of above.
I am thinking of going with the client side so just wanna know how much data ie7 can handle before getting into any memory leak issue.
I would like to know how much data ie7 can handle. I will have around 2000 rows with 4 columns. Shall I go with client side processing. As we know there are lot of benefit you get with this awesome library at client side and response time is very fast.
I can see couple of pros and cons
Server side :
Pros
1) I am using hibernate so there will lot of object going to create if I send all the data in one request which could be avoided if I request minimum data.
2) User will not see stale data cause data will be in sync with server database most of the cases.
cons)
1) I have to code all the features more code means more bug :)
2) There will be lot of request for search feature.
Client Side just opposite of above.
I am thinking of going with the client side so just wanna know how much data ie7 can handle before getting into any memory leak issue.
This discussion has been closed.
Replies
It might be worth writing a small script which will generate a sample table and see what kind of performance you get from the 2000 rows. I suspect with only 4 columns, it should be okay, but it's certainly towards the point where I'd be considering using server-side processing. Firefox and friends will fly through the 2000 rows, but IE7 is going to huff and puff a bit...
Regarding your two con points:
1. Have a look at the server-side gallery: http://datatables.net/development/server-side/ . There are a number of ready to go scripts (although obviously will need some modification for your DB schema) which might help.
2. There are ways to reduce the number of requests:
Pipelining: http://datatables.net/examples/server_side/pipeline.html
Adding a small filtering delay: http://datatables.net/plug-ins/api#fnSetFilteringDelay
Regards,
Allan