akulkarni

10 ms·

1. 61.▲
   by akulkarni 5y ago

   Hi there, not sure how you did your price comparison, but typically with native compression, performance improvements, continuous aggregates, etc, you can go much further with the same resources on Timescale Cloud than Cloud SQL (or any oth
2. 62.▲
   by akulkarni 5y ago

   Thanks for letting me know. Have you filed a Github issue? If so, could you point me to it? Thanks! https://github.com/timescale/timescaledb
3. 63.▲
   by akulkarni 5y ago

   +1 We agree that the world needs more PostgreSQL and TimescaleDB educational content, and welcome any help!
4. 64.▲
   by akulkarni 5y ago

   Nope :-) That's another product :-D
5. 65.▲
   by akulkarni 5y ago

   Thank you :-) There's a lot of lessons I've learned along the way These are probably two of the top ones: 1. Solve a big problem that people have (even better if you personally have it) 2. Who you work with matters more than what
6. 66.▲
   by akulkarni 5y ago

   Hi there, sorry you had a negative experience with Timescale Cloud. It's true that on Azure we require both the resource group name and also the Virtual Network name to be in lowercase. But Microsoft names are case-agnostic, so this sh
7. 67.▲
   by akulkarni 5y ago

   In our benchmarks (which you and others are welcome to replicate), Timescale vastly outperformed AWS Timestream: https://www.timescale.com/blog/timescaledb-vs-amazon-timestr...
8. 68.▲
   by akulkarni 5y ago

   (Timescale co-founder / CEO) I just want to say that we wouldn't be here without the support, feedback -- and yes, even the honest critiques -- from the HN community. So thank you everyone. As we like to say, we've come a lon
9. 69.▲
   by akulkarni 5y ago

   First of all: Life is worth living. Your son needs you, your family needs you, your friends need you. Even if this is a minor thought in the back of your head, please talk to someone about it. Second, being a new dad is hard! I’ve been ther
10. 70.▲
    by akulkarni 5y ago

    This made me chuckle. Man, what a time capsule: Ready to challenge reality? Take a mind-bending ride through an alternate universe with The Matrix. And on DVD, this year's coolest thriller looks even gnarlier. Get ready to follow t
11. 71.▲
    by akulkarni 5y ago

    As co-founder of another database company in the PostgreSQL ecosystem, I have to say that I'm really impressed with the quality and velocity of launches from the Supabase team. Nothing else to add, except please keep up the great work!
12. 72.▲
    by akulkarni 5y ago

    If you would like to discuss facts: We have witnessed 100,000s+ of different time-series workloads over the past 4.5 years, and the patterns they share may surprise you. There is much more similarity than you may think - similarities that h
13. 73.▲
    by akulkarni 5y ago

    (Timescale co-founder) I'll answer this here with a similar response that I gave Pradeep (the author) via Twitter. I think ClickHouse is a great technology. It totally beats TimescaleDB for OLAP queries. I'll be the first to admit
14. 74.▲
    by akulkarni 5y ago

    I have no doubt that, as usual, akulkarni will make a good PR job / community outreach to explain why, numbers and experience be damned, TimescaleDB is better! I don't like responding to bullies and people who enter dialog
15. 75.▲
    by akulkarni 5y ago

    (Timescale co-founder) Thank you for noticing :-) This is really a testament to all of the amazing products, new features, R&D, and overall work that the team has been shipping. We are firing on all cylinders. Move fast without breaking
16. 76.▲
    by akulkarni 5y ago

    I could go on, but I think these points illustrate that ClickHouse has a different set of design choices for different problems. I would never use it for eCommerce, but it's great for analytics. I agree with this. You are poki
17. 77.▲
    by akulkarni 5y ago

    StackGres by Ongres, which achieved 1.0.0 status today, is another example of someone storing logs in TimescaleDB: https://twitter.com/ongresinc/status/1451194886795849742 (Also, thank you GordonS for the kind wor
18. 78.▲
    by akulkarni 5y ago

    > No, you're not there yet: doing timeseries with timescale is way riskier than with clickhouse, which is both a bit older (not much) and more mature (much more), while also being more widely used This is not true at all, and we exp
19. 79.▲
    by akulkarni 5y ago

    > In my experience, in about 1% of the cases, yes, timescale will be a better choice (ex: if you do very small batches of insertions, if you need to remove some datapoints) but in 99% of the usecases for a time series database, clickhous
20. 80.▲
    by akulkarni 5y ago

    Minor correction: It is actually a 40+ node cluster :-)
21. 81.▲
    by akulkarni 5y ago

    (TimescaleDB co-founder) Thank you for the feedback - it is conversations like this that enable us to understand how we can continue to make TimescaleDB better. And some of the ideas you are discussion are on our roadmap - if anyone wants t
22. 82.▲
    by akulkarni 5y ago

    (TimescaleDB co-founder) 6,000,000 rows inserted per second is great! And if you need that for your workload, then you probably should choose ClickHouse over TimescaleDB (well at least, for now ;-) The reason we don't include that in t
23. 83.▲
    by akulkarni 5y ago

    If you are referring to this post: https://altinity.com/blog/clickhouse-for-time-series That post was written in November 2018 - 3 years ago - when TimescaleDB was barely 1.0. A lot has changed since then: 1. Timescale
24. 84.▲
    by akulkarni 5y ago

    Thanks for sharing. "infinite scalability" is something we are aiming for in our new vision for Timescale Cloud: https://blog.timescale.com/blog/announcing-the-new-timescale... We are not there today, but we
25. 85.▲
    by akulkarni 5y ago

    Also, the team picked `->` as the operator, which I thought was a very natural and intuitive choice :-) e.g., SELECT device_id, timevector(ts, val) -> sort() -> delta() -> abs() -> sum() as volatility
26. 86.▲
    by akulkarni 5y ago

    (TimescaleDB co-founder) Agree - what would you need to see in PostgreSQL / TimescaleDB to enable you to switch from Big Query? We are all ears :-)
27. 87.▲
    by akulkarni 5y ago

    Thanks for reading that article :-)
28. 88.▲
    by akulkarni 5y ago

    TimescaleDB performs quite well. One of our unique insights is that it is quite possible to build a best-in-class time-series database on top of Postgres (although it’s not easy ;-) Here is one benchmark: https://blog.timescale.c
29. 89.▲
    by akulkarni 5y ago

    If you like Postgres, you may want to try TimescaleDB, which is a time-series database built on Postgres (packaged as a Postgres extension). Postgres database + time-series database all in one. This btw is one of the reasons I love Postgres
30. 90.▲
    by akulkarni 5y ago

    (TimescaleDB co-founder) Thanks for the mention, and I completely agree :-) Personally, there is a lot in this article that is misguided. For example, it essentially defines "time-series database" as "metric store." As T