update wsl benchmarks

pull/22/head
romkatv 6 years ago
parent 73e20123a7
commit d1a1bf6325

@ -183,30 +183,18 @@ POWERLEVEL9K_BACKGROUND_JOBS_FOREGROUND=black
function custom_rprompt() echo -E "hello world" function custom_rprompt() echo -E "hello world"
``` ```
Here's the same benchmark for Windows Subsystem for Linux (WSL) with Here's the same benchmark for Windows Subsystem for Linux (WSL) with zsh running in the standard
zsh running in the standard Command Prompt (`cmd.exe`). Command Prompt (`cmd.exe`).
| Theme | / | ~/testrepo | ~/nerd-fonts | ~/linux | | Theme | / | ~/nerd-fonts |
|----------------------------------|----------:|-----------:|-------------:|------------:| |---------------------|----------:|-------------:|
| powerlevel9k/master | 313 ms | 531 ms | 693 ms | 5898 ms | | powerlevel9k/master | 313 ms | 693 ms |
| powerlevel9k/next | 119 ms | 278 ms | 442 ms | 5710 ms | | powerlevel9k/next | 119 ms | 442 ms |
| powerlevel10k | 66 ms | 237 ms | 399 ms | 5569 ms | | **powerlevel10k** | **16 ms** | **19 ms** |
| **powerlevel10k with gitstatus** | **22 ms** | **30 ms** | **30 ms** | **5098 ms** | | naked zsh | 16 ms | 16 ms |
| naked zsh | 16 ms | 16 ms | 16 ms | 16 ms |
Once again Powerlevel10k wins hands down.
Here Powerlevel10k with [gitstatus](https://github.com/romkatv/gitstatus) has even bigger
advantage over Powerlevel9k and manages to render prompt with low latency.
However, every theme failed miserably on the humongous Linux kernel repo, showing prompt latency
over 5 seconds. This might be related to some sort of system cache that can fit indices of
smaller repos but not of Linux kernel. To work around this problem, you can instruct
[gitstatus](https://github.com/romkatv/gitstatus) to not scan dirty files on repos with over 4k
files in the index (see `GITSTATUS_DIRTY_MAX_INDEX_SIZE` in
[gitstatus docs](https://github.com/romkatv/gitstatus)). Linux kernel is the only repo in these
benchmarks that is over this threshold. Its prompt latency goes down to 32 ms but the prompt no
longer shows whether there are dirty (unstaged or untracked) files. It does helpfully indicate
with the color that there _might_ be such files.
## What's the catch? ## What's the catch?

Loading…
Cancel
Save