cgit has some nice design features: for one, it directly uses libgit.a out of a git build, so it accesses data directly and as fast as git does. Also, every query internally produces a "cache" object for display. The cache objects then are designed to output to (and be read from) a static file-system cache if you turn on that option, so even a slow query will only be slow once.
cgit = super-fast
cgit has some nice design features: for one, it directly uses libgit.a out of a git build, so it accesses data directly and as fast as git does. Also, every query internally produces a "cache" object for display. The cache objects then are designed to output to (and be read from) a static file-system cache if you turn on that option, so even a slow query will only be slow once.
-
blog moved
As described elsewhere, I've quit LiveJournal. If you're interested in my continuing posts, you should look at one of these (each contains feed…
-
dremel
They published a paper on Dremel, my favorite previously-unpublished tool from the Google toolchest. Greg Linden discusses it: "[...] it is capable…
-
treemaps
I finally wrote up my recent adventures in treemapping, complete with nifty clickable visualizations.
- Post a new comment
- 0 comments
- Post a new comment
- 0 comments
