3 ms·
hey I'm from the SWE-grep team - feel free to ask me any questions :)
by silasalberti 1y ago
hey I'm from the SWE-grep team - feel free to ask me any questions :)
- daralthus 1y agothis would be useful outside of coding. could you release a benchmark so we can have more models tuned for this?
- bluelightning2k 1y agoNo question just wanted to say good job and thanks as a user. Same with deepwiki and codemaps.
- kwillets 1y agoAre you actually using grep here? How much data are you searching?
- swyx 1y agono - grep is just the closest analogy/use case that we have for it. if we end up releasing the CLI it should be as handy and nobrainer as using ripgrep idk what you expect from a question about "how much data". its tool based search. its a lot.
- kwillets 1y agoI'm just learning about agentic search so I'm a bit adrift. One of my side projects is a full text index for pattern search, and I'm trying to understand how it might fit with that. You mention tool call overhead, but is that a significant part of the latency in the multi-turn scenario, or is it the coding agent being forced into a serial processing pattern?
- swyx 1y agohey sorryjust saw this. i do think its majority serial processing, BUT, parallel calling the same tools also gets issues that i honestly havent spent the time to dig into (something something locks and threading). all i know is ive been stuck in very very super slow/tool calls myself in Windsurf/other AI IDEs and that was a drag. for another take on latency attribution see https://x.com/silasalberti/status/1979310181424206143 https://x.com/silasalberti/status/1979310181424206143
- llllm 1y agoDid you intend to answer them, or you just wanted the questions?
- foodbaby 1y agoWhat base model did you use?