4 ms·

Yeah, this is a known issue, unfortunately--but it's definitely something we want to fix as we improve Warp. See more information here where we chat with Casey

• Aeolun 5y ago
  > we should generally be at, or near, the performance of Alacritty > evidence that it’s not > Yeah, this is a known issue I don’t want to be critical, but which is it? If you know you are not anywhere near the performance, why say you are?
  • bitwize 5y ago
    > If you know you are not anywhere near the performance, why say you are? (in a voice like Jon Lovitz as Master Thespian) Marketing!
  • akho 5y ago
    I don’t see the contradiction. They should be, but they aren’t.
  • cieplik 5y ago
    Hey - that's a good point. The thing about terminal benchmarks is that there are many of them, each focusing on a different aspect and producing different results. There's one by alacritty team[1] that we used in our initial tests[2], there's another ones mentioned in the comments above etc. When using vtbench, Warp performed much better than iterm, for example. Ideally we'd ace all of them, but we're not there yet. Anecdotally, many of our users mention speed/performance improvements over other terminal apps a lot in our Discord! [1] https://github.com/alacritty/vtebench https://github.com/alacritty/vtebench [2] https://www.warp.dev/blog/how-warp-works https://www.warp.dev/blog/how-warp-works