71–80 of 173 posts
Earlier quoted context omitted.
chrome on osx Version 84.0.4147.89 (Official Build) (64-bit) works fine in safari, something is up with the dark theme.
I tried with the same setup and it works fine. I tried to disable JS too and it's OK. Could it be a rogue extension?
Any plans on integration with Apache Arrow?
Any plans on integration with Apache Arrow?
It has been asked here: https://github.com/questdb/questdb/issues/261 . Definitely on our road map. It would be good if you could share your story why you need arrow?
Appreciate the issue link :)
Can you add a tldr?
I noticed there is "Clustering" mentioned under enterprise features, but I can't seem to find any references to it in the documentation. Is this something that will be strictly closed source?
- TCP-based replication for WAN - UDP-based replication for LAN and high traffic environments
We are currently building foundation elements of this replication, such as column-first and parallel writes. These will go into and always be part of QuestDB. TCP-replication will go on top of this foundation and also part of QuestDB. UDP-based replication will be a part of a different product we are building that will be named Pulsar.
Congrats! I've been looking for a time series database but most of them seems to be in-memory nosql databases. QuestDB might be exactly what I need. I'll definitely give it a try soon!
How does your performance compare to Atlas? [0] [0] https://github.com/Netflix/atlas
I have not tried to benchmark Atlas but I am not sure the result would be meaningful. Atlas is an in-memory database, QuestDB persists to disk, the 2 are not very comparable.
It stores recent data in memory for increased performance which is replicated across instances and then persists to S3 for long term storage, making aggregates queryable and full resolution data available with a delay for a restore from storage.
Am I the only one that's like "wtf is a time-series database compared to a normal one?"
This is actually an underrated question. Time-series databases offer better performance and usability for dealing with time-series data (think DevOps metrics, data from IoT devices, stock prices etc, anything where you're monitoring and analyzing how things change over time) They allow you answer questions where time is the main component of interest much more quickly and easily: eg 1: IoT Sensors) Show me the averag…
This is so incredibly frustratingly slow to pull on FactSet and Capital IQ, it makes me want to pull my hair every time I have to build line charts over time for a period greater than 2 years