New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compare various SQL database implementations #579
Comments
SQLite is generally known to perform well for smaller applications:
MySQL is generally known to perform well for larger applications:
|
IRC #postgresql (11/20/14 ~ 7:10pm EST):
IRC #drupal 11/20/14 ~ 7:10pm EST):
IRC #python 11/20/14 ~ 8:10pm EST):
IRC ##php 11/20/14 ~ 8:50pm EST):
|
The following indicates language support across the various databases:
|
MariaDB generally outperforms MySQL, supports more languages than PostgresSQL, and is an acceptable database platform for common content management systems such as Drupal. Also, like MySQL, MariaDB supports phpMyAdmin. Since this project implements both php, python, and may consider a content management system (i.e. drupal), MariaDB will be attempted. Note: MariaDB can be implemented on the Raspberry Pi. |
I saw some of your comments on IRC. And you are completely wrong about language support, I think all those languages must have PostgreSQL drivers, and I know for sure that at least the following do: Java, Perl, Python, Ruby, Tcl, C#, Node-JS, Go. In fact, in PostgreSQL about page is listed, and I quote: "There are interfaces for Java (JDBC), ODBC, Perl, Python, Ruby, C, C++, PHP, Lisp, Scheme, and Qt just to name a few". So checking which language both support is just pointless, as both support the most languages out there. Also, it supports all (and a lot of others) languages as procedural languages inside the database. Which is great as many machine learning libraries are implemented in languages such as Python or R and you can use those inside the database (specially madlib, which is Python and specific for PostgreSQL). Still for machine learning, PostgreSQL has a powerful support for arrays and index those very well with GIN and GiST, and can perform KNN search out of box. Disclaimer: Clearly I'm a PostgreSQL guy, so my comments are biased. Although before you actually choose one, I recommend you testing those in practice with your application (it is even OK to support them all for some time during the development), you should learn at least the basics of which and do some more advanced work (guys on IRC can help a lot), and test performance too with different database sizes (but keep in mind you might need some tuning on them for optimal performance), I surely did that before noticing that I wanted to be a "PostgreSQL guy", ;-). |
This is really a worthless comparison. It's the same as comparing a Ford to a Chevy, a screwdriver to a hammer, McDonalds to Burger King, Christianity to Buddhism. There is no "best". Stated your requirements, and use the product that fits that description. |
IRC #machinelearning 11/22/14 ~ 3:20pm EST):
|
We will research the best SQL database implementation for both the SVM related data, and its corresponding web-interface (i.e. user administration).
Important aspects to consider, include whether a given database is supported by various common content management systems (i.e. drupal, wordpress), provides a phpMyAdmin equivalent, supports both php and python, and scales well for large projects.
The text was updated successfully, but these errors were encountered: