On Tue, May 6, 2014 at 5:12 AM, Dr Eberhard Lisse <e...@lisse.na> wrote: > Jeff > > It's in MySQL, at the moment roughly 1.8 GB, if I pull it into a > dataframe it saves to 180MB. I work from the dataframe. > > But, it's not only a size issue it's also a speed issue and hence I > don't care what I am going to use, as long as it is fast. > > sqldf is easy to understand for me but it takes ages. If > alternatives were roughly similar in speed I would remain with > sqldf. > > dplyr sounds faster, and promising, but the intrinsic stuff is > way beyond me (elderly Gynaecologist) on the learning curve...
You can create indices in sqldf and that can speed up processing substantially for certain operations. See examples 4h and 4i on the sqldf home page: http://sqldf.googlecode.com. Also note that sqldf supports not only the default SQLite backend but also MySQL, h2 and postgresql. See ?sqldf for info on using sqldf with MySQL and the others. ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.