![]() ![]() I can remove them individually, file by file. This output shows that the binaries are my largest files. = All paths by reverse accumulated size =įormat: unpacked size, packed size, date deleted, path name git/filter-repo/analysis/path-all-sizes.txt Looking in path-all-sizes.txt, I see the files along with their path and size: $ cat. git/filter-repo/analysis folder here's what is in mine: $ ls -1. To analyze a repo using git-filter-repo, I use the following command: $ git filter-repo -analyze ![]() It's available to install on Linux, as well as Windows (through Scoop) and macOS (through Homebrew). Instead, I use a fantastic tool called git-filter-repo. I can do this using Git but it isn't an easy job. I can see in Git that the following files are in the folder: $ git show -pretty="" 6ac1e2cīinary files /dev/null and b/build/app.v1 differīefore I can fix this, I need a way to see what is in my Git history. Pay special attention to each commit and the size of the repo: $ git log -oneline I'll begin by cloning my repository using -bare and -mirror: git clone -bare -mirror let's take a look at what is in the repository. Walking through an example might make this easier to understand. It isn't enough to clean up your repo you also need to remove sensitive files that you could accidentally send to someone. However, if you do this often enough, you end up with what I call a bloated Git repository. Git will remove the file but keep it available in case you need it later. You can, of course, remove files with the git rm command. ![]() So, if you send something by mistake to your repo, like a build file, temporary folder, your cache, and so forth, Git will store it because it can't predict when you make mistakes. I tried mounting with the async flag, and with rwsize boosted, and it made little difference.Git is an amazing tool for tracking all your changes and reverting them if necessary. I'm not sure whether statsd and lockd are running over TCP and UDP. ![]() The system mounting the volume is running OSX Mavericks.Īt the moment the main nfsd connection is running over UDP, which seems ideal over a virtual connection. The owner of the volume is running Ubuntu 12.10 (Quantal), with default settings. # local driveĠ.3600 0.4800 0.5150 0.5552 0.5400 1.4500Ĭlearly some latency is inevitable, but this is bad enough that it makes some simple tasks quite painful. The first: dd if=/dev/zero of=test bs=16 count=16384Įach result is based on 100 samples. Obviously NFS performance will be worse than writing straight to a local SSD, but the NFS is just running over a virtual private network interface with Virtualbox. Cloning a small repository into the mounted NFS drive can take a couple of minutes (5-10 seconds on a local drive). The performance of this is extremely poor: it often takes up to 5 seconds just to run git status. Git (and related tools like sourcetree) are run in OSX, on the shared directory. In order to support inotify inside the linux machine, we eschew the usual method of sharing directories with VirtualBox: instead, the Virtualbox machine exposes an NFS share, which is mounted in OSX. I manage a vagrant setup for our developers running OSX to manage VirtualBox systems for development. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |