sirffuzzylogik

12 ms·

1. 61.▲
   Automatic brightness adjustment based on screen contents(github.com)

   1 points by sirffuzzylogik 6y ago|0 comments
2. 62.▲
   by sirffuzzylogik 6y ago

   Everyone seems to be blaming the "bad" (relatively, I personally don't believe that) performance of FF on Gecko. But is that the case? Isn't it mostly because of many websites relying heavily on JS while V8 is much faste
3. 63.▲
   by sirffuzzylogik 6y ago

   I agree that our blog post lacks of details, here are some: - PostgreSQL 12 - 12 - No - We ran the test using the pg_prewarm [0] module, the difference was negligible Regarding the "toy" query, the reason we are showcasing this in
4. 64.▲
   by sirffuzzylogik 6y ago

   This is on the roadmap, we will work on integrating with https://github.com/timescale/tsbs , TSBS has Victoria Metrics support too.
5. 65.▲
   by sirffuzzylogik 6y ago

   Thanks Jan!
6. 66.▲
   by sirffuzzylogik 6y ago

   Not yet but this is on the roadmap. In the meantime you could use a filesystem that supports compression such as ZFS or brtfs. The data is column orientated, this means that compression would be super efficient.
7. 67.▲
   by sirffuzzylogik 6y ago

   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?
8. 68.▲
   by sirffuzzylogik 6y ago

   What browser are you using?
9. 69.▲
   by sirffuzzylogik 6y ago

   Thanks for reporting this! This is an old link, please use https://questdb.io/docs/guide/crud instead. I am currently updating the README and removing all dead links.
10. 70.▲
    by sirffuzzylogik 6y ago

    This is a great idea, we will have a look! It is good to see that the ecosystem is moving towards a normalized / "standard" benchmarking tool.
11. 71.▲
    by sirffuzzylogik 6y ago

    j1897 is referring to https://questdb.io/blog/2020/04/02/using-simd-to-aggregate-b...
12. 72.▲
    by sirffuzzylogik 6y ago

    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.
13. 73.▲
    by sirffuzzylogik 6y ago

    As you said, performance is the main differentiator. We are orders of magnitude faster than TimescaleDB and InfluxDB on both data ingestion and querying. TimescaleDB relies on Postgres and has great SQL support. This is not the case for Inf
14. 74.▲
    by sirffuzzylogik 6y ago

    PostgREST is an interesting project, thanks! I will check how good is our support for them. It really depends on how tailored to Postgres they are, if they only rely on the Wire protocol then it should be fine!
15. 75.▲
    by sirffuzzylogik 6y ago

    Thanks for your feedback, I am pleased to know that you like it! - This is a c5.metal instance (AWS) with 48 physical cores and 192 GB of memory. We use only 24 of those 48 cores. - If I understand your example well, the query "select
16. 76.▲
    by sirffuzzylogik 6y ago

    Thank you for your thoughts! 1. We do plan to support full SQL functionalities, we have a pretty good subset already [1]. I think that what we do is more than "naive memory bandwidth bench code", however I am happy to listen and w
17. 77.▲
    by sirffuzzylogik 6y ago

    We already support the Postgres Wire protocol, it is still in alpha though. You can check the documentation here: https://questdb.io/docs/guidePSQL/ We do not implement 100% of the protocol yet, but the plan it to
18. 78.▲
    by sirffuzzylogik 6y ago

    I have mixed feelings about this feature actually. It's super handy and nice when browsing the Web while going through a lot of pages in a short amount of time. When using proper Web apps it's a total pain + sometimes the history
19. 79.▲
    by sirffuzzylogik 6y ago

    Sorry for the frustration guys, this was not meant to be "something to lock people in". The rationale for doing this was to prevent macOS users from going back when scrolling the grid horizontally. I submitted a PR to remove this
20. 80.▲
    by sirffuzzylogik 6y ago

    Thanks for the feedback. A PR was created to fix this :) : https://github.com/questdb/questdb/pull/434
21. 81.▲
    by sirffuzzylogik 7y ago

    The numbers are impressive, especially because it is against kdb. q/kdb is mostly finance focused and closed source so not really flexible. questdb has an advantage on this, it might be a bit of a tangent but I wonder if this could be
22. 82.▲
    by sirffuzzylogik 7y ago

    How does it compare to kdb performance wise?