Git packfiles use delta compression, storing only the diff when a 10MB file changes by one line, while the objects table stores each version in full. A file modified 100 times takes about 1GB in Postgres versus maybe 50MB in a packfile. Postgres does TOAST and compress large values, but that’s compressing individual objects in isolation, not delta-compressing across versions the way packfiles do, so the storage overhead is real. A delta-compression layer that periodically repacks objects within Postgres, or offloads large blobs to S3 the way LFS does, is a natural next step. For most repositories it still won’t matter since the median repo is small and disk is cheap, and GitHub’s Spokes system made a similar trade-off years ago, storing three full uncompressed copies of every repository across data centres because redundancy and operational simplicity beat storage efficiency even at hundreds of exabytes.
美國到底在幹什麼？伊朗戰爭正在動搖中國的雄心
。新收录的资料是该领域的重要参考
Getting into a sleep routine。新收录的资料对此有专业解读
吴恩达表示，距离实现该目标仍有数十年距离，且随着公开互联网数据接近枯竭，单纯依赖扩大参数规模来提升智能的路径正面临挑战。，更多细节参见新收录的资料