andreybavt

3 ms·

1. 1.▲
   by andreybavt 4mo ago

   Hi, thanks for trying it! 19m for ~20 tables is slower that I'd expect, I assume you activated historic queries, right? As Luca said we're focusing on performance improvements right now. 99% of the latency is LLM calls, so we&#x27
2. 2.▲
   by andreybavt 4mo ago

   good point! yes, there's a feedback mcp tool that agents are instructed to use when they want to save/update ktx "memories". This is a way to keep the wiki+semantic layer up to date beyond the initial ingestion. Plus eve
3. 3.▲
   by andreybavt 4mo ago

   Hopefully more agents and fewer PowerPoints and McKinsey folks in the future :)
4. 4.▲
   by andreybavt 4mo ago

   yes, exactly
5. 5.▲
   by andreybavt 4mo ago

   When you install ktx, you'll have to initialize the project directory and ktx initializes a git repo there to assure the version controls. ktx project directory is self-contained. The main 2 parts inside are : - wiki: a collection of .
6. 6.▲
   by andreybavt 4mo ago

   Thanks! ktx maintainer here, related to the queries sandbox question, we're attacking this problem from a different angle: instead of catching bad queries at runtime we try to make it impossible to generate a bad query. ktx allows agen
7. 7.▲
   by andreybavt 4mo ago

   Thanks! yes, exactly. But what you described is just half of what ktx does, we call it "wiki" - self organizing collection of ingested markdown files. The second (equally important) part of ktx is similarly self-organizing executa
8. 8.▲
   by andreybavt 4mo ago

   yep, happy to share more details with you @modus-tollens if you're interested
9. 9.▲
   by andreybavt 4mo ago

   Great questions! we're currently working on Spider 2 submission, hope to have first results soon. It's true that we took file-first approach and not a graph DB. Main reason is that the ktx wiki and semantic layer entities while be
10. 10.▲
    by andreybavt 4mo ago

    Agreed, in addition to this I'd say it's better to spend tokens once while ingesting the sources and storing the canonical reusable definition rather than having agents do the full exploration over and over again
11. 11.▲
    by andreybavt 4mo ago

    Hey, ktx maintainer here! Great question, we actually have quite a bit in common with Wren, they're in the same category. The main difference is that with Wren you author the semantic model (write MDL) and it executes SQL through its
12. 12.▲
    gRPC tunnel to reverse the client-server communication(giskard.ai)

    3 points by andreybavt 4y ago|1 comments