Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use gix-status to get file changed status #1

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

eatradish
Copy link
Member

No description provided.

@eatradish
Copy link
Member Author

eatradish commented Jan 14, 2025

check aosc-os-abbs (untracked file):

saki@MagMilk [ [email protected] ] $ hyperfine -i --prepare 'sync; echo 3 | sudo tee /proc/sys/vm/drop_caches' '/home/saki/bash-git-status/target/release/bash-git-status' 'bash-git-status'
Benchmark 1: /home/saki/bash-git-status/target/release/bash-git-status
  Time (mean ± σ):     273.2 ms ±   9.2 ms    [User: 106.8 ms, System: 514.7 ms]
  Range (min … max):   249.1 ms … 281.8 ms    10 runs

  Warning: Ignoring non-zero exit code.

Benchmark 2: bash-git-status
  Time (mean ± σ):     354.8 ms ±   8.5 ms    [User: 57.1 ms, System: 533.2 ms]
  Range (min … max):   336.8 ms … 368.6 ms    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  /home/saki/bash-git-status/target/release/bash-git-status ran
    1.30 ± 0.05 times faster than bash-git-status

check aosc-os-abbs (changes file):

saki@MagMilk [ [email protected] ] $ hyperfine -i --prepare 'sync; echo 3 | sudo tee /proc/sys/vm/drop_caches' '/home/saki/bash-git-status/target/release/bash-git-status' 'bash-git-status'
Benchmark 1: /home/saki/bash-git-status/target/release/bash-git-status
  Time (mean ± σ):     105.3 ms ±   4.5 ms    [User: 18.8 ms, System: 212.8 ms]
  Range (min … max):    96.6 ms … 110.7 ms    10 runs

  Warning: Ignoring non-zero exit code.

Benchmark 2: bash-git-status
  Time (mean ± σ):     350.3 ms ±   8.7 ms    [User: 57.4 ms, System: 528.6 ms]
  Range (min … max):   335.8 ms … 364.6 ms    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  /home/saki/bash-git-status/target/release/bash-git-status ran
    3.33 ± 0.16 times faster than bash-git-status

Unchanged:

Benchmark 1: /home/saki/bash-git-status/target/release/bash-git-status
  Time (mean ± σ):     274.1 ms ±   8.9 ms    [User: 111.7 ms, System: 509.5 ms]
  Range (min … max):   256.3 ms … 284.8 ms    10 runs

  Warning: Ignoring non-zero exit code.

Benchmark 2: bash-git-status
  Time (mean ± σ):     350.9 ms ±  10.6 ms    [User: 52.3 ms, System: 529.6 ms]
  Range (min … max):   340.2 ms … 377.7 ms    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  /home/saki/bash-git-status/target/release/bash-git-status ran
    1.28 ± 0.06 times faster than bash-git-status

@eatradish
Copy link
Member Author

eatradish commented Jan 14, 2025

linux get 5x slower with unchanged or untracked:

Benchmark 1: /home/saki/bash-git-status/target/release/bash-git-status
  Time (mean ± σ):      1.567 s ±  0.009 s    [User: 0.185 s, System: 1.061 s]
  Range (min … max):    1.547 s …  1.580 s    10 runs

  Warning: Ignoring non-zero exit code.

Benchmark 2: bash-git-status
  Time (mean ± σ):     316.9 ms ±   8.2 ms    [User: 108.7 ms, System: 699.8 ms]
  Range (min … max):   307.1 ms … 332.7 ms    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  bash-git-status ran
    4.95 ± 0.13 times faster than /home/saki/bash-git-status/target/release/bash-git-status

changed:

Benchmark 1: /home/saki/bash-git-status/target/release/bash-git-status
  Time (mean ± σ):      87.1 ms ±   2.1 ms    [User: 24.4 ms, System: 153.6 ms]
  Range (min … max):    84.1 ms …  91.1 ms    10 runs

  Warning: Ignoring non-zero exit code.

Benchmark 2: bash-git-status
  Time (mean ± σ):     314.9 ms ±  10.1 ms    [User: 110.4 ms, System: 683.4 ms]
  Range (min … max):   299.4 ms … 327.3 ms    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  /home/saki/bash-git-status/target/release/bash-git-status ran
    3.62 ± 0.15 times faster than bash-git-status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant