JoshDev
JoshDev6mo ago

Langfuse v3 timeline

https://langfuse.com/docs/roadmap#%EF%B8%8F-upcoming-breaking-changes Is there any sort of timeframe for when those breaking changes (moving to a multi docker setup) is going to be? we have langfuse in prod at the moment but getting pretty bad latency for the dashboard/trace/session screens when we are under high load from users. Presuming this setup is for that usecase? we've been hesistant to upgrade or start customising with that on the horizon. Sorry i know timelines are hard and we are genuinely really happy with langfuse so far just this question mark we are wondering about
Roadmap - Langfuse
Sneak peak into upcoming new features and changes in Langfuse. This page is updated regularly.
3 Replies
Marc
Marc6mo ago
Hi @JoshDev, we’ve been avoiding this on Langfuse cloud by scaling out the database for now but have high urgency to get to the v3 setup quickly. As we want to test this thoroughly and provide a good migration path, there is not a timeline on this yet. We’ll make sure to announce this here once there’a an early version to try Interesting about your comment is latency on traces/generations tables. Usually we see issues on dashboard analytical queries with single projects that have a larger scale (to be fixed with a olap db)
JoshDev
JoshDev6mo ago
Thank you, i'll keep tabs in here that would be really helpful - is there going to be any breaking schema changes or migrations required/planned so far? just concious of how we extend the DB/build our filtering and analytics pages around the existing filtering system
Marc
Marc5mo ago
Generally the db schema is never covered by semver (might break with any release), the public api is covered by it and includes tests to check for breaking changes. If you build donstream usecases I'd heavily suggest to use the API If APIs are missing, let's chat about them on github discussions or feel free to open a PR to add them