Very interesting. I do a lot of time based graphing and have been using OpenFlashChart and it's compliment plugin for rails. Since I've been doing it so long, I have the math and accumulators down fairly pat, but I'm always looking for something to make my life easier.
But I have two questions for you: 1) Can it handle pulling data from existing sets? I already have my tables down and don't really want to change them, or change how they are populated.
2) Will Rifgraf, or more precisely AmCharts, handle large data sets? I'm talking 20K-30k points over a couple of years?
adamheroku
· 1 year ago
1) You could do a mass import by looping through your data and posting one point at a time. If you wanted to keep the data in its current location, you could modify the amstock_settings.xml to point at a different location for the data, or change the app to do an external call to load the data instead of its own database.
2) amcharts caps out at 20k I believe, which leads me to believe it can handle up to that number smoothly.
Anonymouse
· 1 year ago
This is a really cool hack, but I have some issues:
1) It stores all data as strings -- even the timestamps. (Umm, why?) 2) The client gets all data for a graph every time it starts up (zooming is done locally, server is no longer involved) 3) The server constructs the data as a CSV file in memory (not even trying to stream it) 4) If you take the 20K limit as a given, that's 2 years of hourly activity, Or 13 days of minutely activity.
Jeff Vyduna
· 8 months ago
Hi Adam! This is Jeff from Poll Everywhere (another YC Company) - Could you possibly add a crossdomain.xml to the root of rifgraf so my offsite flash could pull the CSV data from it?
We love rifgraf. So simple, and makes so much sense.
adamheroku
· 8 months ago
Cool, glad you're enjoying it!
If you want a change, fork it on github, and then send me a pull request. Or fork and deploy your own copy on Heroku, which should be as simple as git clone, heroku create, git push heroku master. :)
Jeff Vyduna
· 8 months ago
Thanks! I have to remember how easy Heroku makes it to copy entire apps!
/usr/local/lib/ruby/1.8/net/http.rb:560:in `initialize': Invalid argument - connect(2) (Errno::EINVAL) from /usr/local/lib/ruby/1.8/net/http.rb:560:in `open' from /usr/local/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/local/lib/ruby/1.8/timeout.rb:53:in `timeout' from /usr/local/lib/ruby/1.8/timeout.rb:93:in `timeout' from /usr/local/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/local/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/local/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:123:in `transmit' from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:49:in `execute_inner' from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:39:in `execute' from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:17:in `execute' from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient.rb:65:in `get' from ./doit.rb:7
All Comments
But I have two questions for you:
1) Can it handle pulling data from existing sets? I already have my tables down and don't really want to change them, or change how they are populated.
2) Will Rifgraf, or more precisely AmCharts, handle large data sets? I'm talking 20K-30k points over a couple of years?
2) amcharts caps out at 20k I believe, which leads me to believe it can handle up to that number smoothly.
1) It stores all data as strings -- even the timestamps. (Umm, why?)
2) The client gets all data for a graph every time it starts up (zooming is done locally, server is no longer involved)
3) The server constructs the data as a CSV file in memory (not even trying to stream it)
4) If you take the 20K limit as a given, that's 2 years of hourly activity, Or 13 days of minutely activity.
We love rifgraf. So simple, and makes so much sense.
If you want a change, fork it on github, and then send me a pull request. Or fork and deploy your own copy on Heroku, which should be as simple as git clone, heroku create, git push heroku master. :)
But the charting seems to misbehave.
/usr/local/lib/ruby/1.8/net/http.rb:560:in `initialize': Invalid argument - connect(2) (Errno::EINVAL)
from /usr/local/lib/ruby/1.8/net/http.rb:560:in `open'
from /usr/local/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/local/lib/ruby/1.8/timeout.rb:53:in `timeout'
from /usr/local/lib/ruby/1.8/timeout.rb:93:in `timeout'
from /usr/local/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/local/lib/ruby/1.8/net/http.rb:553:in `do_start'
from /usr/local/lib/ruby/1.8/net/http.rb:542:in `start'
from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:123:in `transmit'
from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:49:in `execute_inner'
from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:39:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient/request.rb:17:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/rest-client-1.0.3/lib/restclient.rb:65:in `get'
from ./doit.rb:7