Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAsked remote read write #4243
Comments
This comment has been minimized.
This comment has been minimized.
|
I think you will get a better answer for that in the devs Malling list |
This comment has been minimized.
This comment has been minimized.
|
@krasi-georgiev thanks |
MoSunDay
closed this
Jun 11, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
MoSunDay commentedJun 8, 2018
I wonder why some remote storage only provides a write operation, not a read, so how can the data written to the database be used?
From other if using remote read and wirte InfluxDB, every time a large number of queries memory is required for a double, because InfluxDB need memory cache results, and then give P8S results to vomit, P8S also need to save data memory, and then execute PromQL.
This is just my guess. Why not set a time period for the InfluxDB data to exist locally after it has been fetched? Future queries will only use P8S 'own memory overhead.