This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 511
Use influxDB instead of MySql for timeseries [V2 Feature Request] #154
Labels
Comments
I use SQLite for my database which both stores and reads tick data, it's faster than Arctic which was designed for tick data. Optimize after measuring, not before. |
I rather prefer the previous plans of using "PyStore" for data storage (or SQLite+SQLAlchemy, if it MUST be SQL, with SQLAlchemy is easier to use another database). I just do "daily" trading so for me it is an additional pain to keep database servers "spinning" 24/7. |
Didn't even know about pystore. Nice. I tested with parquet myself but
found it inferior (if you can believe it) to storing and retrieving
compressed data frames from SQLite
…On Sun., Jun. 7, 2020, 4:29 a.m. FrithiofJensen, ***@***.***> wrote:
I rather prefer the previous plans of using "PyStore" for data storage (or
SQLite+SQLAlchemy, if it MUST be SQL, with SQLAlchemy is easier to use
another database). I just do "daily" trading so for me it is an additional
pain to keep database servers "spinning" 24/7.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJDE4VA2LUO22PHXJ7TZEE3RVNFVXANCNFSM4NNL4DTA>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
InfluxDB is a well performing Open Source DB which suits the timeseries functionality better than MySql. It might be an idea supporting this DB.
The text was updated successfully, but these errors were encountered: