Thanks VixWiz, The "excessive calling" of the modifier under:
Firefox ( Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)) 1655 rows of data resulting in 820 grouped rows calls the modifier 9091 times IE 7.0.5730.13 (my colleague reports the same results under IE 8) 1655 rows of data resulting in 820 grouped rows calls the modifier 69353 times. and Chrome 3.0.195.27 1655 rows of data resulting in 820 grouped rows calls the modifier 44639 times. I am finding that the visualization under IE with a couple thousand rows of data will likely be unusable by the end user. Modifying the data before passing it to the group function is helping. I am grouping the data three different ways and displaying them via bar, pie and timeline charts. With the fixup IE still complains (but less). I am worried that the poor performance on IE for google.visualization.data.group will be true of other visualizations. IE does not need help to run javascript apps poorly - it can do that all by itself. Are there any guidelines on how much data I should using to ensure that the visualization will work under IE? I have 8 columns of data (1 datetime and the others are numbers and short strings) with 1655 rows, the table visualization is OK, but the bar chart complains about "a script on this page is causing Internet Explorer to run slowly ...". Thanks, Gary On Oct 18, 7:48 am, VizWiz <[email protected]> wrote: > Hi, > > We are aware that the grouping function can be optimized for cases where the > input has modifier functions on the keys. We may have a fix to that in the > next versions of the API. > > In the meantime, you can try running the modifier function on the input > yourself before passing it to the grouping function. > > Also, can you please provide the name/version of the browsers where this > becomes a problem? > > Cheers, > VizWiz > > > > On Thu, Oct 15, 2009 at 4:18 PM, magila <[email protected]> wrote: > > > I created a custom modifier for the group key that truncates a > > datetime field to 15 minute intervals and it gets called more than I > > expect. This is OK with firefox and chrome, but with browsers that > > don't like long running javascript, it is becoming a problem. The > > modifier seems to be called ((NumberOfRows of the input datatable)-1) > > *5 + (NumberOfRows of Resultant datatable) + 1 > > > If I get 1631 rows from a query against a google spreadsheet and it > > results in 802 keys, my modifier function gets called 8953 times! > > > Is this expected? Is there a more efficient way to do this? > > > Below are the snippets of javascript > > > var timeGroupedData = google.visualization.data.group(data,[{'column': > > 0, 'modifier':whichQuarterHour, 'type':'datetime'}],[{'column': 0, > > 'aggregation': google.visualization.data.count, 'type': 'number'}]); > > > function whichQuarterHour(someDate) { > > someDate.setMinutes(Math.floor(someDate.getMinutes()/15) * 15); > > someDate.setSeconds(0); > > someDate.setMilliseconds(0); > > gqcounter +=1; > > return someDate; > > } --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
