Hi, The various visualizations themselves do not have programmatical limitations on data set size. However they have other limitations: The image charts have roughly a ~2K data limit (as they are based on the Charts API vis which have this limit due to URL size limits). Other charts run in the browser and, obviously, overloading them with huge data-sets will cause slow performance or other issues due to memory size in browsers.
It is important, though, to practice smart coding. Consider that the average screen cannot display more than 1.5K data points horizontally for example. Effectively, users cannot absorb more than several 100s of data points (depending on the exact chart type used). There is really no point in sending huge data sets to the client if they cannot be viewed by the user. Drill-downs can be implemented as subsequent requests to the server, etc. Hope this helps. On Thu, Nov 27, 2008 at 5:41 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote: > > Hi, > Noob here. Just viewed the IO session. Very impressed! > > There's mention of providing performance metrics in the talk. > > My cursory reading of the docs didn't seem to make this obvious. > Wondering how big of a dataset the various widgets can handle. > > Would appreciate any estimates - or where the bottle necks lie > so I can better understand how to build an application. > > thanks, > -sr > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
