benchcaddy 0.1.0__tar.gz

benchcaddy-0.1.0/LICENSE

@@ -0,0 +1,174 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright
+owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with that
+entity. For the purposes of this definition, "control" means (i) the power,
+direct or indirect, to cause the direction or management of such entity,
+whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or
+more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source, and
+configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object
+code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that is
+included in or attached to the work (an example is provided in the Appendix
+below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that
+is based on (or derived from) the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative Works
+shall not include works that remain separable from, or merely link (or bind by
+name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the purposes
+of this definition, "submitted" means any form of electronic, verbal, or
+written communication sent to the Licensor or its representatives, including
+but not limited to communication on electronic mailing lists, source code
+control systems, and issue tracking systems that are managed by, or on behalf
+of, the Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise designated in
+writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this
+section) patent license to make, have made, use, offer to sell, sell, import,
+and otherwise transfer the Work, where such license applies only to those
+patent claims licensable by such Contributor that are necessarily infringed by
+their Contribution(s) alone or by combination of their Contribution(s) with the
+Work to which such Contribution(s) was submitted. If You institute patent
+litigation against any entity (including a cross-claim or counterclaim in a
+lawsuit) alleging that the Work or a Contribution incorporated within the Work
+constitutes direct or contributory patent infringement, then any patent
+licenses granted to You under this License for that Work shall terminate as of
+the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy
+of this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that
+You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any
+part of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of the
+following places: within a NOTICE text file distributed as part of the
+Derivative Works; within the Source form or documentation, if provided along
+with the Derivative Works; or, within a display generated by the Derivative
+Works, if and wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and do not modify the
+License. You may add Your own attribution notices within Derivative Works that
+You distribute, alongside or as an addendum to the NOTICE text from the Work,
+provided that such additional attribution notices cannot be construed as
+modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a
+whole, provided Your use, reproduction, and distribution of the Work otherwise
+complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any
+character arising as a result of this License or out of the use or inability to
+use the Work (including but not limited to damages for loss of goodwill, work
+stoppage, computer failure or malfunction, or any and all other commercial
+damages or losses), even if such Contributor has been advised of the
+possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole
+responsibility, not on behalf of any other Contributor, and only if You agree
+to indemnify, defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason of your
+accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+Copyright 2026 Matthias Lenga
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+	http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

benchcaddy-0.1.0/MANIFEST.in

@@ -0,0 +1,4 @@
+include README.md
+include LICENSE
+include benchcaddy_logo.png
+include examples/benchmark_nonlinear_transform.py

benchcaddy-0.1.0/PKG-INFO

@@ -0,0 +1,242 @@
+Metadata-Version: 2.4
+Name: benchcaddy
+Version: 0.1.0
+Summary: Lightweight benchmark sweeps with environment capture.
+Author: Matthias Lenga
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/MatthiasLen/BenchCaddy
+Project-URL: Repository, https://github.com/MatthiasLen/BenchCaddy
+Project-URL: Issues, https://github.com/MatthiasLen/BenchCaddy/issues
+Keywords: benchmark,performance,profiling,cli,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: System :: Benchmark
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: sqlalchemy>=2.0.41
+Requires-Dist: typer>=0.12.5
+Requires-Dist: rich>=13.9.4
+Requires-Dist: gitpython>=3.1.43
+Requires-Dist: psutil>=6.1.1
+Provides-Extra: dev
+Requires-Dist: pytest>=8.3; extra == "dev"
+Dynamic: license-file
+
+<img src="./benchcaddy_logo.png" alt="BenchCaddy logo" width="240"></img>
+
+We all tell ourselves we’re going to use Scalene,PyInstrument or TorchProfile - tools that produce traces so complex and beautiful they belong in a modern art gallery. But let’s be real: most days, "benchmarking" is just us sprinkling time.time() across our code like frantic seasoning on a failing dish. You’re staring at the terminal, trying to remember if the last run was actually faster or if you just happen to be in a better mood, only to realize you’ve already lost the thread. *"Wait, when did I change the naming convention of the log files? Is 'results_v2_final' newer than 'results_new_test'?"*
+
+
+**BenchCaddy** is the humble sidekick for those of us living in that chaotic middle ground. It replaces "vibes-based" timing with stabilized sweeps and environment metadata, tucking everything into a neat database before your brain can wander. It won’t map your entire soul, but it will save you from your own memory and provide a summary clean enough to make you look like the organized professional your friends think you are. No traces to decipher, no lost logs, and no more gaslighting yourself - just actual proof your code is getting faster.
+
+# Something missing ?
+
+BenchCaddy is intentionally lean. I built it to curb my own occasional "log-file-chaos," but I’m curious how you manage yours. If you’ve got a feature idea, a bug that’s getting on your nerves, or a suggestion for an export format that actually belongs in this decade, open an issue. I’m not trying to build a bloated enterprise behemoth; I just want this to be the best way to track performance without ever having to name a file timings_final_v4_fixed_REALLY.log again.
+
+
+## Quick start
+
+BenchCaddy is designed around two steps:
+
+1. Run a benchmark sweep over one or more configurations.
+2. Inspect or compare the recorded results from the database (e.g. using the CLI).
+
+This example stays self-contained and benchmarks a nonlinear iterative transform
+with two variants and two input sizes.
+
+```python
+import math
+
+from benchcaddy import Sweep, observe
+
+
+def initial_signal(size: int) -> list[float]:
+    return [
+        math.sin(index * 0.013) + 0.5 * math.cos(index * 0.007)
+        for index in range(size)
+    ]
+
+
+@observe("nonlinear_iteration")
+def nonlinear_iteration(values: list[float], variant: str) -> list[float]:
+    next_values: list[float] = []
+    for value in values:
+        transformed = (
+            math.tanh(value * 1.4)
+            + 0.75 * math.sin(value * value + 0.2)
+            + 0.25 * math.cos(value - 0.1)
+        )
+        if variant == "stabilized":
+            transformed += 0.05 * value * value
+        else:
+            transformed += 0.03 * math.exp(-(value * value))
+        next_values.append(transformed)
+    return next_values
+
+
+def benchmark_case(size: int, variant: str) -> float:
+    values = initial_signal(size)
+    for _ in range(8):
+        values = nonlinear_iteration(values, variant)
+    return sum(abs(value) for value in values)
+
+
+Sweep(
+    target=benchmark_case,
+    params={
+        "size": [512, 2048],
+        "variant": ["baseline", "stabilized"],
+    },
+    suite_name="nonlinear-transform",
+    samples=5,
+    warmup_iterations=1,
+    verbose=True,
+).run()
+```
+
+BenchCaddy writes samples, medians, observations, and environment metadata to
+`benchcaddy.db` in the current working directory.
+
+The full runnable example lives in the repository and source distribution at
+[`examples/benchmark_nonlinear_transform.py`](https://github.com/MatthiasLen/BenchCaddy/blob/main/examples/benchmark_nonlinear_transform.py)
+and supports `--verbose`, `--database`, `--samples`, and `--warmup-iterations`.
+
+`Sweep` also accepts a script path as the target. In that mode, parameter keys
+are mapped to CLI flags such as `size -> --size` and `warmup_runs` / `iterations`
+can be used as aliases for `warmup_iterations` / `samples`.
+
+## Sweep options
+
+The main public `Sweep(...)` options are:
+
+- `samples`: number of measured samples per configuration
+- `iterations`: alias for `samples`
+- `warmup_iterations`: warmup runs before sampling begins
+- `warmup_runs`: alias for `warmup_iterations`
+- `database_path`: store results in a specific SQLite file instead of `./benchcaddy.db`
+- `lock_cpu_affinity`: preserve the current CPU affinity set before benchmarking
+- `sync`: callable used to synchronize async device work after each invocation
+- `reporter`: custom reporter implementing the `SweepReporter` protocol
+- `verbose=True`: use the built-in Rich reporter during execution
+
+## Script targets
+
+You can benchmark a standalone script instead of a Python callable:
+
+```python
+from benchcaddy import Sweep
+
+
+Sweep(
+    target="./train_step.py",
+    params={
+        "size": [512, 2048],
+        "variant": ["baseline", "stabilized"],
+        "use_cache": [True, False],
+    },
+    suite_name="train-step",
+    samples=5,
+).run()
+```
+
+BenchCaddy converts configuration keys to CLI flags:
+
+- `size=512` becomes `--size 512`
+- `use_cache=True` becomes `--use-cache`
+- `use_cache=False` becomes `--use-cache false`
+
+That mode works best with scripts that parse explicit values for non-presence
+flags and exit with status code `0` on success.
+
+## CLI and inspect results
+
+List all recorded suites:
+
+```bash
+benchcaddy list
+```
+
+`list` also shows the observation labels seen across runs in each suite.
+
+Show the recorded runs and environment for a suite:
+
+```bash
+benchcaddy show nonlinear-transform
+```
+
+Show the detailed timings for a single recorded run:
+
+```bash
+benchcaddy show 12
+benchcaddy show 2.3
+```
+
+Composite run IDs use `SWEEP_ID.RUN_INDEX`, so `2.3` means the third run in
+the second recorded sweep.
+
+Show multiple runs side by side in a suite-style view:
+
+```bash
+benchcaddy show 4 2.3 1.2
+```
+
+Compare configurations within a suite by median runtime:
+
+```bash
+benchcaddy compare nonlinear-transform
+```
+
+Compare a suite against a selected recorded run instead of the best run:
+
+```bash
+benchcaddy compare nonlinear-transform 2.4
+```
+
+Restrict a suite comparison to runs that match selected configuration keys from
+the reference run:
+
+```bash
+benchcaddy compare nonlinear-transform 2.4 --strict size
+benchcaddy compare nonlinear-transform 2.4 --strict size variant
+benchcaddy compare nonlinear-transform 2.4 --strict variant
+```
+
+Compare two specific runs directly. Improvements greater than 5% are shown in
+green and regressions greater than 5% are shown in red:
+
+```bash
+benchcaddy compare 12 15
+benchcaddy compare 2.3 3
+```
+
+For more detail in the inspection output, add `--verbose`:
+
+```bash
+benchcaddy --verbose show nonlinear-transform
+benchcaddy --verbose compare nonlinear-transform
+```
+
+## How to read the output
+
+- `Mean +- Std (s)` is the arithmetic mean and sample standard deviation across benchmark samples
+- suite comparisons are ranked by median runtime, not by the mean column
+- `Best Median (s)`, `Delta vs Best`, and direct-run `Median Delta` / `Median Percent Change` all use median runtime
+- observation tables report per-label timing aggregated across samples
+- `Total (s)` in observation tables is the sum across all samples for that label
+
+## Environment metadata
+
+Every recorded run stores environment details alongside the timing data, including:
+
+- Python version and operating system string
+- CPU model and total system memory
+- GPU model when it can be detected
+- Git branch, commit hash, and dirty state when run inside a Git repository
+- process metadata such as PID, priority, affinity, and RSS memory

benchcaddy-0.1.0/README.md

@@ -0,0 +1,211 @@
+<img src="./benchcaddy_logo.png" alt="BenchCaddy logo" width="240"></img>
+
+We all tell ourselves we’re going to use Scalene,PyInstrument or TorchProfile - tools that produce traces so complex and beautiful they belong in a modern art gallery. But let’s be real: most days, "benchmarking" is just us sprinkling time.time() across our code like frantic seasoning on a failing dish. You’re staring at the terminal, trying to remember if the last run was actually faster or if you just happen to be in a better mood, only to realize you’ve already lost the thread. *"Wait, when did I change the naming convention of the log files? Is 'results_v2_final' newer than 'results_new_test'?"*
+
+
+**BenchCaddy** is the humble sidekick for those of us living in that chaotic middle ground. It replaces "vibes-based" timing with stabilized sweeps and environment metadata, tucking everything into a neat database before your brain can wander. It won’t map your entire soul, but it will save you from your own memory and provide a summary clean enough to make you look like the organized professional your friends think you are. No traces to decipher, no lost logs, and no more gaslighting yourself - just actual proof your code is getting faster.
+
+# Something missing ?
+
+BenchCaddy is intentionally lean. I built it to curb my own occasional "log-file-chaos," but I’m curious how you manage yours. If you’ve got a feature idea, a bug that’s getting on your nerves, or a suggestion for an export format that actually belongs in this decade, open an issue. I’m not trying to build a bloated enterprise behemoth; I just want this to be the best way to track performance without ever having to name a file timings_final_v4_fixed_REALLY.log again.
+
+
+## Quick start
+
+BenchCaddy is designed around two steps:
+
+1. Run a benchmark sweep over one or more configurations.
+2. Inspect or compare the recorded results from the database (e.g. using the CLI).
+
+This example stays self-contained and benchmarks a nonlinear iterative transform
+with two variants and two input sizes.
+
+```python
+import math
+
+from benchcaddy import Sweep, observe
+
+
+def initial_signal(size: int) -> list[float]:
+    return [
+        math.sin(index * 0.013) + 0.5 * math.cos(index * 0.007)
+        for index in range(size)
+    ]
+
+
+@observe("nonlinear_iteration")
+def nonlinear_iteration(values: list[float], variant: str) -> list[float]:
+    next_values: list[float] = []
+    for value in values:
+        transformed = (
+            math.tanh(value * 1.4)
+            + 0.75 * math.sin(value * value + 0.2)
+            + 0.25 * math.cos(value - 0.1)
+        )
+        if variant == "stabilized":
+            transformed += 0.05 * value * value
+        else:
+            transformed += 0.03 * math.exp(-(value * value))
+        next_values.append(transformed)
+    return next_values
+
+
+def benchmark_case(size: int, variant: str) -> float:
+    values = initial_signal(size)
+    for _ in range(8):
+        values = nonlinear_iteration(values, variant)
+    return sum(abs(value) for value in values)
+
+
+Sweep(
+    target=benchmark_case,
+    params={
+        "size": [512, 2048],
+        "variant": ["baseline", "stabilized"],
+    },
+    suite_name="nonlinear-transform",
+    samples=5,
+    warmup_iterations=1,
+    verbose=True,
+).run()
+```
+
+BenchCaddy writes samples, medians, observations, and environment metadata to
+`benchcaddy.db` in the current working directory.
+
+The full runnable example lives in the repository and source distribution at
+[`examples/benchmark_nonlinear_transform.py`](https://github.com/MatthiasLen/BenchCaddy/blob/main/examples/benchmark_nonlinear_transform.py)
+and supports `--verbose`, `--database`, `--samples`, and `--warmup-iterations`.
+
+`Sweep` also accepts a script path as the target. In that mode, parameter keys
+are mapped to CLI flags such as `size -> --size` and `warmup_runs` / `iterations`
+can be used as aliases for `warmup_iterations` / `samples`.
+
+## Sweep options
+
+The main public `Sweep(...)` options are:
+
+- `samples`: number of measured samples per configuration
+- `iterations`: alias for `samples`
+- `warmup_iterations`: warmup runs before sampling begins
+- `warmup_runs`: alias for `warmup_iterations`
+- `database_path`: store results in a specific SQLite file instead of `./benchcaddy.db`
+- `lock_cpu_affinity`: preserve the current CPU affinity set before benchmarking
+- `sync`: callable used to synchronize async device work after each invocation
+- `reporter`: custom reporter implementing the `SweepReporter` protocol
+- `verbose=True`: use the built-in Rich reporter during execution
+
+## Script targets
+
+You can benchmark a standalone script instead of a Python callable:
+
+```python
+from benchcaddy import Sweep
+
+
+Sweep(
+    target="./train_step.py",
+    params={
+        "size": [512, 2048],
+        "variant": ["baseline", "stabilized"],
+        "use_cache": [True, False],
+    },
+    suite_name="train-step",
+    samples=5,
+).run()
+```
+
+BenchCaddy converts configuration keys to CLI flags:
+
+- `size=512` becomes `--size 512`
+- `use_cache=True` becomes `--use-cache`
+- `use_cache=False` becomes `--use-cache false`
+
+That mode works best with scripts that parse explicit values for non-presence
+flags and exit with status code `0` on success.
+
+## CLI and inspect results
+
+List all recorded suites:
+
+```bash
+benchcaddy list
+```
+
+`list` also shows the observation labels seen across runs in each suite.
+
+Show the recorded runs and environment for a suite:
+
+```bash
+benchcaddy show nonlinear-transform
+```
+
+Show the detailed timings for a single recorded run:
+
+```bash
+benchcaddy show 12
+benchcaddy show 2.3
+```
+
+Composite run IDs use `SWEEP_ID.RUN_INDEX`, so `2.3` means the third run in
+the second recorded sweep.
+
+Show multiple runs side by side in a suite-style view:
+
+```bash
+benchcaddy show 4 2.3 1.2
+```
+
+Compare configurations within a suite by median runtime:
+
+```bash
+benchcaddy compare nonlinear-transform
+```
+
+Compare a suite against a selected recorded run instead of the best run:
+
+```bash
+benchcaddy compare nonlinear-transform 2.4
+```
+
+Restrict a suite comparison to runs that match selected configuration keys from
+the reference run:
+
+```bash
+benchcaddy compare nonlinear-transform 2.4 --strict size
+benchcaddy compare nonlinear-transform 2.4 --strict size variant
+benchcaddy compare nonlinear-transform 2.4 --strict variant
+```
+
+Compare two specific runs directly. Improvements greater than 5% are shown in
+green and regressions greater than 5% are shown in red:
+
+```bash
+benchcaddy compare 12 15
+benchcaddy compare 2.3 3
+```
+
+For more detail in the inspection output, add `--verbose`:
+
+```bash
+benchcaddy --verbose show nonlinear-transform
+benchcaddy --verbose compare nonlinear-transform
+```
+
+## How to read the output
+
+- `Mean +- Std (s)` is the arithmetic mean and sample standard deviation across benchmark samples
+- suite comparisons are ranked by median runtime, not by the mean column
+- `Best Median (s)`, `Delta vs Best`, and direct-run `Median Delta` / `Median Percent Change` all use median runtime
+- observation tables report per-label timing aggregated across samples
+- `Total (s)` in observation tables is the sum across all samples for that label
+
+## Environment metadata
+
+Every recorded run stores environment details alongside the timing data, including:
+
+- Python version and operating system string
+- CPU model and total system memory
+- GPU model when it can be detected
+- Git branch, commit hash, and dirty state when run inside a Git repository
+- process metadata such as PID, priority, affinity, and RSS memory