Unresponsive script

blueicreate

First off. This is an amazing plugin!

One issue I'm having is using the script with a large amount of data. For example, I initially used the script with a table of about 40 records and it worked like a charm. Then I added 2000 records to the table and now I get "unresponsive script" error messages. Is there only a cap to the number of records this script can handle?

allan

Hi blueicreate,

There is no upper limit on the number of rows that DataTables can deal with - it's more of a javascript engine issue (as you are seeing here). Having said that, it would be most disappointing (and a bit surprising) if it can't cope with 2000 records. Do you have a link you can post (you can send it to me directly if you don't want to make it public: http://www.datatables.net/contact )?

One thing that is definitely worth trying with this many records is disabling the sorting classes - which are seriously bog down even the fastest javascript engine due to all of the DOM interaction it needs to do:
http://datatables.net/usage#bSortClasses

Regards,
Allan

blueicreate

Actually, this would be much easier to explain over the phone. Would you be available for a quick chat? I will gladly pay you for your time.

allan

Hi blueicreate,

If you send me a message with your e-mail address, I'll get back to you: http://www.datatables.net/contact

Allan

allan

To let anyone else know who looks at this post, having had the opportunity to speak to blueicreate, it was clear that server-side processing ( http://datatables.net/1.5-beta/examples/data_sources/server_side.html ) was the way to go here. Server-side processing is ideal for massive data chucks since this is what database engines do best (unlike javascript ;-) ).

Allan

BBoy_Vlad

Hi, i'm having this problem too, but i'm using "Server-side Processing" when i do query that returns smalls amounts of data ( below 100 records) it works fine, but if i reach above 150 or 200 records it stays loading forever... acctually i need to work with 2000 or more records... any clue of what may be wrong?

johnsam

so server side processing is the best way?

allan

When dealing with 2000+ records - yes, server-side processing is probably the way to go. If you can forget IE then 5000 records might be the cut off point. Server-side processing however will cope with many millions - limited only by your server.

Allan

johnsam

Hi allan,

I have done the server side processing and using JSON format to display the records but getting unresponsive script message even for mozilla and IE.. any thoughts or suggestions?

Thanks in advance :)

bidon

Any resolution on this? Ironically, I added 2000 to the page size. I get the same issue around 450 records!

Granted, I'm using about every plugin imaginable, but still. And yes, this is server-side processing.

bidon

Actually, I found disabling firebug helped. It had to be totally disabled, not having it running on the page didn't work.

But this is only 450 records, so if anyone has any comments...

allan

I don't understand why 450 records would slow down server-side processing. It should cope with millions of rows without issue. Do you have paging disabled or something? Can you link me to the page?

Allan