![]() ![]() ![]() I do wish to caution that the "comparison" in its current state probably isn't very fair.įor example, the amount of work isn't exactly equal between git-grep and ripgrep the git-grep filtered several subtrees after-the-fact ( | grep -v), whereas the ripgrep got those same subtrees as an -ignore-file, so could prune early.Īlso: the comparison where git-grep won used -word-regexp (on both ripgrep and git-grep), the comparison where rg won had plain strings without word-boundaries. I've included the (censored) commands we ran below. It was a fairly brute-force approach: dump all "secret" identifiers from the DB (~16.000) into a file, and then do a search with -fixed-strings.įortunately, my colleague shared his results with me, so we can go into more detail if you'd like. I think it's mostly the query that is the problem, it wasn't exactly. git.Īfter ~8 years of development as a "strictly internal" tool, in an academic setting, with quite a bit of contributor rotation, we know there are a lot of sloppy parts, data-privacy wise, so this is a very crude hammer to see how much censoring-work is ahead of us. It's about 4.200 commits, 250 MB in total, of which 110 MB in. We're open-sourcing our in-house data management platform, and this grep was to see if any of our real data was left over anywhere in the history, e.g. That’s either one really big repository or a very resource constrained machine. ![]() That’s incredible and actually kind of unexpected. Termcolor 1.0 is out and moved to its own repository ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |