| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Lsat modified 2014-12-30
|
|
|
|
|
|
At first I used multithreading because threading would still run with
one CPU core due to the GIL. That probably happened because I accessed
_hashes[algos] in the loop of _queue_updater. Now that this is not
done anymore, and only the hash update function is called which releases
the GIL for data larger than 2 KiB, multiple cores are actually used.
For comparison, for a file of 2.3 GiB (min/avg/max/sd secs for n=10):
- pee sha256sum md5sum < file: 16.5/16.9/17.4/.305
- python3 digest.py -sha256 -md5 < file: 13.7/15.0/18.7/1.77
- python2 digest.py -sha256 -md5 < file: 13.7/15.9/18.7/1.64
- jacksum -a sha256+md5 -F '#CHECKSUM{i} #FILENAME': 32.7/37.1/50/6.91
The file is actually 2367029248 bytes, resident in the disk cache.
Environment:
- CPU: Intel i5-460M
- Arch Linux x86_64
- Linux 3.17-rc4
- coreutils 8.23
- moreutils 0.51
- jacksum 1.7.0 on OpenJDK 1.7.0_71
- Python 3.4.2, Python 2.7.8
|
|
Created to "Simultaneously calculate multiple digests (md5, sha256)",
http://unix.stackexchange.com/q/163747/8250
This implementation has a simple single-threaded class (Hasher) and a
multi-threaded one. Currently uses the multithreading.Queue interface.
|
|
Send a notification only if a highlight is found (e.g. when you are
mentioned).
|
|
|
|
mtime: 19 July 2013
|
|
Originally I wanted it to be a git-review post-review hook, but there
seems to be no way to get the most recently pushed commits.
|
|
Just changing the marker does not make selections more apparent.
Increase line thickness and zorder to increase visibility.
|
|
Do not update domain if looking at a previous part, or if the new line
fits in the current graph. This makes it easier to look at older data
while updating the plot.
|
|
|
|
get_diffs() was called in update(), but that would invalidate numbers.
Now the input file is fully read (allows moving).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Shift X axis as time progresses.
|
|
This fixes wrong data updates when the UI gets paused (and as a result,
the data update gets delayed).
|
|
There are often more than 8 lines, use a different set of colors in an
attempt to improve recognition.
|
|
Experiment to visualize updates to /proc/interrupts. "Rarely" used,
hence a subfolder "rare".
|
|
|
|
|
|
|
|
With the "-C" option, a number of columns can be included before
skipping them. Bugfix: reset skip state to avoid eating chars at the
beginning for the next line. Enhancement: ignore EPIPE.
Also adjusted the middle threshold to 9 ("XX..N..XX").
|
|
Previously, the colors were not cleared as an attempt to optimize
printing. New approach (requiring less LOC as well): print color if
it does not equal the current state (previous color).
|
|
Use case: analyse captured TCP traces.
|
|
The `--contains` option (default, enabled via `-vfast=0`) does not
show a result if there is no tag following a commit. The `-vcache_only`
option prevents execution of `git describe` and thereby speeds up
post-processing.
|
|
`--contains` does exactly what I need (show which tag contains the
commit), but it is very slow when getting deeper in the history.
(500 ms vs 30000ms for a subdirectory from v3.0..v3.13-rc1 with 100
commits.
For future reproduction, the command `git log v3.0..v3.13-rc1
drivers/net/wireless/rt2x00 | git-log-describe.awk` takes
12:20 minutes to complete for the slow mode (using `--contains`) where
it is finished in only 19 seconds for the fast mode (using
`--first-parent). After the cache is filled, this time gets reduced to
slightly more than a second.
|
|
|
|
Instead of showing where a commit was derived from, use `--contains` to
show a description relative to a tag containing the commit.
|
|
git-describe is slow, this change allows the output to be cached in
a directory using two levels (first two chars of hash for a directory,
the remaining 38 for the file). Set `-vcache=1` to enable the cache
or specify a custom cache directory with `-vcache_dir=DIR`.
On the Linux tree, this feature decreases the run time from 18 seconds
to just one second (with .git in already in disk cache for both trials
and 466 commits for a certain path).
|
|
Some commits failed to match in an decorated log because they used
a bold-face color (like `\e[1;94m`).
|
|
To avoid funny color effects when doing:
git log --color | git-log-describe.awk | less -RN
|
|
|
|
As of today (2013-11-22) there is still no support for adding an
indication of tag to the output of git log. This script post-processes
the output of `git log` and adds the output of `git describe
--first-parent` to line following the commit ID.
For a version suitable for `git log --oneline`, see [1].
[1]: http://stackoverflow.com/q/17379010/427545
|
|
|
|
|
|
Given a URL (and optionally a subject), determine the patch location and
save to a file based on the sanitized subject line.
|
|
Useful for using git-send-email without storing typing the long
passwords all the time.
|
|
Created at 2012-11-12.
|
|
This script stores compile times while compiling a kernel. It was used
to determine the temperature performance after changing thermal paste.
|
|
|
|
|
|
|
|
- ftp-get: when 'get bar.ext' on ftp.example.com/foo/, the directory
'foo' won't be created.
|
|
|
|
|
