tjh.dev
multitime: init at 1.4
+39
pkgs/tools/misc/multitime/default.nix
+39
pkgs/tools/misc/multitime/default.nix
···
···
1
+
{ stdenv, fetchFromGitHub, autoreconfHook }:
2
+
3
+
stdenv.mkDerivation rec {
4
+
pname = "multitime";
5
+
version = "1.4";
6
+
7
+
src = fetchFromGitHub {
8
+
owner = "ltratt";
9
+
repo = pname;
10
+
rev = "${pname}-${version}";
11
+
sha256 = "1p6m4gyy6dw7nxnpsk32qiijagmiq9vwch0fbc25qvmybwqp8qc0";
12
+
};
13
+
14
+
nativeBuildInputs = [ autoreconfHook ];
15
+
16
+
meta = {
17
+
description = "Time command execution over multiple executions";
18
+
19
+
longDescription = ''
20
+
Unix's `time` utility is a simple and often effective way of measuring
21
+
how long a command takes to run. Unfortunately, running a command once
22
+
can give misleading timings: the process may create a cache on its first
23
+
execution, running faster subsequently; other processes may cause the
24
+
command to be starved of CPU or IO time; etc. It is common to see people
25
+
run `time` several times and take whichever values they feel most
26
+
comfortable with. Inevitably, this causes problems.
27
+
28
+
`multitime` is, in essence, a simple extension to time which runs a
29
+
command multiple times and prints the timing means (with confidence
30
+
intervals), standard deviations, minimums, medians, and maximums having
31
+
done so. This can give a much better understanding of the command's
32
+
performance.
33
+
'';
34
+
35
+
license = stdenv.lib.licenses.mit;
36
+
homepage = "https://tratt.net/laurie/src/multitime/";
37
+
platforms = stdenv.lib.platforms.unix;
38
+
};
39
+
}
+2
pkgs/top-level/all-packages.nix
+2
pkgs/top-level/all-packages.nix