well..... since it's a client based issue I can only say that this is a function of the hardware you're using. If you have a very large datatable the chart rendering will be the same. You must take into account the chart type you're using, for instance, if you're drawing a line/area chart there is no need/significance to a datatable larger than, let's say, 2000 rows since you a large chart to see all items. That's the same with other charts. You can load a very large datatable, either by JSON/Ajax/Spreadsheets or other database connections and modify/query it for chart usage, via grouping or dataviews generation.
I, for instance, use a complex data (multi-level array) structure and before drawing, I create a datatable with all that I need. At the end, I managed to scale my data from 25,000 rows into 1,000. It's much more efficient and fast. You might want to think on your data before dropping large scale data. Just a reminder, this is client side programming, and everything must be light weight, even the data. On Wed, Dec 7, 2011 at 2:14 PM, [email protected] < [email protected]> wrote: > Awesome work. Google always keeps us Googled. > I would like to know how much of data can this visualization can > support. > Is it bench marked? > can it support billion data ? > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-visualization-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
