Many of the fastest-growing and demanding transactional workloads are moving to the new @ClickHouseDB managed @postgres service. DM @saisrirampur if you're interested in learning more.
I spend a lot of time talking about ClickHouse Managed Postgres. But our customers running their businesses on it tell the story much better than I can. 🙏 ❤️
Here are 10 production customers, what they’re building, and why they chose our Managed Postgres. 🧵
The list includes fast-growing AI companies to large enterprises, migrating hundreds of GB to multi-TB databases from Aurora, RDS, Neon and more.
@ClickHouseDB
8/11 @TrainyAI helps AI teams get more out of their GPUs and move faster, from scheduling training workloads to analyzing results with Pluto, their open-source experiment tracker.
They moved Pluto’s transactional database from RDS to ClickHouse Managed Postgres. Initial page loads became 2–3x faster, at lower cost. Postgres runs experiment operations, ClickHouse powers metrics analytics, and both live in ClickHouse Cloud.
https://t.co/5NTwvjOV1H
Over the past five years, I can't count the amount of times I've heard this said about @ClickHouseDB. Now we're bringing that same focus on speed and reliability to Postgres, to create the unified data platform that AI needs.
Thank you @TrainyAI team for all the trust in migrating from RDS Postgres to ClickHouse Managed Postgres. Really appreciate the feedback through the process and glad that performance has been much better on both OLTP and OLAP fronts, post migration.
@roanakb@asaiUwU@ClickHouseDB
.Love testimonials like this! Brings a ton of validation to the hard work team has been putting to build the world's fastest and most reliable Postgres service.
Thank you @asaiUwU for the kind words and all the feedback during the migration. 🙏
@ClickHouseDB
Huge thanks to @ClickHouseDB for the spotlight! We're building the fastest experiment tracker out there and it wouldn't be possible without them.
One user's query took 10-15 min on W&B, 5 seconds on Pluto.
Read below 👇
We caught up with @roanakb and @asaiUwU from @TrainyAI, a @ycombinator company, to learn how switching from Amazon RDS to @ClickHouseDB Managed Postgres helped them make their OSS experiment tracker, Pluto, faster and cheaper to run, while bringing it under one unified roof 👇
https://t.co/ZGmqMIQl7Z
NeptuneAI shuts down March 5th.
@TrainyAI just launched Pluto on @ycombinator, a drop-in replacement so you don't lose years of experiment data.
Swap one import. Dual-log to validate. Export your history.
Open source. On Neptune's official transition hub.
https://t.co/m77bDjdmrx
@TrainyAI's Konduktor platform helps bring the benefits of a leading research team to your GPU cluster. We provide a fault-tolerant scheduler, integrated observability, and more.
Check out our docs: https://t.co/tO0pbT7eu1
This leads to significantly higher (>80%) GPU usage.
Add in some fault-tolerance to the infrastructure, and we see:
- No more manual restarts at 2am.
- ML Engineers get to focus on their jobs, rather than becoming DevOps experts.
Top tier AI research teams (Meta, OpenAI, etc.) have figured out the most efficient way to work with a cluster of GPUs. Instead of managing each GPU separately, they create a pools of GPU nodes and let sophisticated schedulers manage GPU availability efficiently.
At @TrainyAI, we built a controller within Konduktor to monitor GPU node health and isolate unhealthy nodes. This way if a job fails, 0 manual intervention is required. K8s does its magic of placing work only on healthy nodes, and we forward relevant GPU/NCCL logs to your CSP. 🚀
ML engineers shouldn’t be wasting time debugging infrastructure — especially when H100s have a 25-30% fault rate. 🛠️
ML infrastructure should be able to handle bumps and bruises to the underlying hardware.
3/ One of the biggest value-adds of @TrainyAI's Konduktor platform is that we simplify this complexity. We abstract away network configurations, so you can launch multinode training with high-bandwidth networking across different clouds in the same way.
2/ At @TrainyAI, we've seen AI research teams lose over $10,000 trying to scale out due to misconfigured GPU fabrics. That's a costly mistake that can be avoided.