Hi,
I use the Chart API to produce such graphs:
http://www.freevec.org/function/bmove512
but, the data appears to have a bit wrong scaling: here is the Y data:
xdata,512,1024,2048,4096,8192,16384,32768
scalar aligned,678.1684,813.8021,976.5625,1198.2362,1194.5719,1178.3560,975.3433
vector aligned,1743.8616,2712.6736,3616.8981,4155.5851,4542.1512,4200.2688,2037.1578
As it is, it appears to be more than the 5000 MB/s where it only reaches 4542 MB/s! :)
Would you like me to print the output of print_r() on the chart object?
Comments
Comment #1
tjholowaychuk commentedThe print_r would defiantly help I will see what I can do
Comment #2
kmargar commentedHere it is:
Comment #3
tjholowaychuk commentedSeems to be fine, I think this may be an issue with how google charts renders the range labels, "[#end] => 5451" since the range is so large google will simply round it up, this is nothing I have done. You may have to generate the LEFT X-axis labels manually with chart_mixed_axis_label()'s
Unfortunatly the API google provides is not the most robust implementation of charting but at least for the most part it is very simple
Comment #4
kmargar commentedtrue. i changed the max value manually (1.2*max(values)) so as to leave some space above the graph, but apparently it caused some trouble. Now I have just removed the 1.2 and it seems to be working fine, albeit the graph takes the whole chart area.
I guess this is the same reason that causes this, right?
http://www.freevec.org/function/memchr
Comment #5
tjholowaychuk commentedHmm without seeing the code for memchr I cant really say, but as long as it does not have a max set on #adjust_resolution it should be resolving the highest point to '100' which would just be the top of the chart so it should not have cutoff like that
Comment #6
tjholowaychuk commentedits to bad that there are size limitations on these images as well, the labels get pretty cluttered on the bottom, hopefully Google will address this
Comment #7
tjholowaychuk commentedComment #8
kmargar commentedHi again,
I sent this email to the google charts api forum, I got this reply, any idea what he means?
http://groups.google.com/group/google-chart-api/browse_thread/thread/b97...
Comment #9
tjholowaychuk commentedHmm, I am not sure what to say, wish I could help more but I have not had problems with adjust_resolution being set to TRUE the values have always been resolved properly between the 0 and 100 points
Comment #10
kmargar commentedCould you check that thread again (last reply)? Perhaps he found the problem causing this.
Comment #11
tjholowaychuk commentedHmm I see there are alot of new features released I will take look at these, as well as your issue, and get back to you ASAP.
Comment #12
tjholowaychuk commented