Hi Renata, It depends on how many of those data points you want to render simultaneously in a chart inside a client.
You can easily have datasources holding and serving that many (and more) data on the server side. You can also send a reasonable chunk of those datapoints to the client, but the bottleneck is how many of those datapoints you are actually going to display inside a chart. Since Google Charts are rendered using SVG, every datapoint is rendered as an SVG node in the page DOM. Most browsers will start breaking down if you try to visualize something of the order of tens of thousands of datapoints (because the DOM of the page will then contain tens of thousands of nodes, making drawing and layout operations very slow). So as long as you display in your charts only a fraction of those 500K data points (because you perform explicit subsampling or filtering) you should be fine: in experiments I have, I have gone up to scatterplots with ~30K visualized datapoints at the same time (and roughly 10x total datapoints, out of which those 30k are sampled) with somewhat bearable performances (on Chrome). If you try to cram all 500K datapoints in a single chart it won't work afaik. Normally, it becomes confusing even for the user to have more than a few thousand datapoints in a single chart, so this rendering limitation might not be as hard as you'd expect. /R. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/bExDUXQybEViNDRK. 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.
