Git Push Output Numbers Explained | Generated by AI

Home 2026.02

Question: Explain these numbers in this git push output

Answer:

This is a typical output from git push when you send new commits to GitHub (or another Git remote). Here’s a breakdown of what each line and number actually means:

Delta compression using up to 8 threads

Git is compressing the data you’re sending using delta compression (storing changes relative to other objects instead of full copies).
It decided to use up to 8 CPU threads to do this compression in parallel.

Compressing objects: 100% (4/4), done.

Git compressed 4 objects (usually commits + trees + blobs).
All 4 were successfully compressed → 100% (4/4).

Writing objects: 100% (4/4), 2.44 KiB | 2.44 MiB/s, done.

Git wrote 4 objects to the packfile that will be sent.
Total size of these objects (after compression) = 2.44 KiB
Writing speed during this local pack creation = 2.44 MiB/s

Total 4 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.

On GitHub’s side:

Transferred: sent 6904, received 4540 bytes, in 18.9 seconds

Total network traffic during this push:

Bytes per second: sent 364.8, received 239.9

Effective transfer speeds (very low in this case):

To github.com:lzwjava/blog-source.git

The final line just shows which remote repository you pushed to.

Quick summary – what was actually sent?

This kind of output is typical when:

References:


Back Donate