You have two issues here: the first is actually getting the data from the server and the second is the quantity of data processed in the browser.
In the first case, you have set up 5 DataTables, all with exactly the same number of rows (which could just be a coincidence I guess, but it doesn't seem likely). If those DataTable do in fact have the exact same number of rows, all based on the same "frames", then you could consolidate them into one DataTable (which would shave some of the data download off by eliminating duplicate data) and use DataViews to slice the data into whatever you need for your charts and controls. Assuming you are not doing any intensive computational work on that data set, modern browsers should be more than capable of handing a 10000 row data set. If that is still loading too slow, you could set up a data source on your server to send data to the client in chunks. Instead of loading the data directly on page load, use an AJAX request to query the server for chunks of data and pull them down one by one, assembling your charts as you go, until you have all of the data. For the second part, the primary slow down is when you have too many data points graphed in a single chart. If memory serves, the charts can reasonably handle data sets up to one row per pixel width of the chartArea section of the chart (the part where the lines/bars/etc are drawn). Any more than that, and you start to run into performance problems. Using ChartRangeFilters like you are should help with this part. If that still gives performance problems, then you might want to consider aggregating your data for display in the charts. Perhaps instead of including data for every frame, you could include data for every 5 frames, grouped together. On Friday, November 8, 2013 9:15:51 AM UTC-5, [email protected] wrote: > > Hi, > > in my company we're using google charts as a way to display and analyze > results of benchmark runs in our visualization software. Depending on the > run length and frame rate we collect quite some data. In many cases this is > too much for the current versions of chrome or firefox to display within 30 > seconds. Are there ways to speed this up? We'd love to see the pages > displayed within 5-10 seconds, but currently I have to hit "wait for > result" twice for the page attached until it is displayed. Also, > interaction gets quite difficult the larger the data set. > > I'd appreciate any help. > Ronny > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/groups/opt_out.
