Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This package provides a SAC interface by the W3C. SAC is an interface for CSS parsers.
This package provides a SAC interface by the W3C. SAC is an interface for CSS parsers.
This package provides a SVG 1.0 interface.
Batik is a Java-based toolkit for applications or applets that want to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as display, generation or manipulation.
This package provides XMLGraphics constants (originally from batik).
The Boehm-Demers-Weiser conservative garbage collector can be used as a garbage collecting replacement for C malloc or C++ new. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory that is no longer useful. The collector automatically recycles memory when it determines that it can no longer be otherwise accessed.
The collector is also used by a number of programming language implementations that either use C as intermediate code, want to facilitate easier interoperation with C libraries, or just prefer the simple collector interface.
Alternatively, the garbage collector may be used as a leak detector for C or C++ programs, though that is not its primary goal.
The Boehm-Demers-Weiser conservative garbage collector can be used as a garbage collecting replacement for C malloc or C++ new. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory that is no longer useful. The collector automatically recycles memory when it determines that it can no longer be otherwise accessed.
The collector is also used by a number of programming language implementations that either use C as intermediate code, want to facilitate easier interoperation with C libraries, or just prefer the simple collector interface.
Alternatively, the garbage collector may be used as a leak detector for C or C++ programs, though that is not its primary goal.
The Boehm-Demers-Weiser conservative garbage collector can be used as a garbage collecting replacement for C malloc or C++ new. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory that is no longer useful. The collector automatically recycles memory when it determines that it can no longer be otherwise accessed.
The collector is also used by a number of programming language implementations that either use C as intermediate code, want to facilitate easier interoperation with C libraries, or just prefer the simple collector interface.
Alternatively, the garbage collector may be used as a leak detector for C or C++ programs, though that is not its primary goal.
The Boehm-Demers-Weiser conservative garbage collector can be used as a garbage collecting replacement for C malloc or C++ new. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory that is no longer useful. The collector automatically recycles memory when it determines that it can no longer be otherwise accessed.
The collector is also used by a number of programming language implementations that either use C as intermediate code, want to facilitate easier interoperation with C libraries, or just prefer the simple collector interface.
Alternatively, the garbage collector may be used as a leak detector for C or C++ programs, though that is not its primary goal.
This C library provides semi-portable access to hardware-provided atomic memory update operations on a number of architectures. These might allow you to write code that does more interesting things in signal handlers, write lock-free code, experiment with thread programming paradigms, etc.
The Phoronix Test Suite is a comprehensive testing and benchmarking platform that provides an extensible framework for which new tests can be easily added. It can carry out both qualitative and quantitative benchmarks in a clean, reproducible, and easy-to-use manner, making it easy to compare one particular setup against another one.
Locust is a performance testing tool that aims to be easy to use, scriptable and scalable. The test scenarios are described in plain Python. It provides a web-based user interface to visualize the results in real-time, but can also be run non-interactively. Locust is primarily geared toward testing HTTP-based applications or services, but it can be customized to test any system or protocol.
Note: Locust will complain if the available open file descriptors limit for the user is too low. To raise such limit on a Guix System, refer to info guix --index-search=pam-limits-service-type.
The time utility is a simple and often effective way of measuring how long a command takes to run (wall time). Unfortunately, running a command once can give misleading timings. multitime is, in essence, a simple extension to time which runs a command multiple times and prints the timing means, standard deviations, mins, medians, and maxes having done so. This can give a much better understanding of the command's performance.
vkmark offers a suite of scenes that can be used to measure various aspects of Vulkan performance. The way in which each scene is rendered is configurable through a set of options.
BenchExec is a framework for reliable benchmarking, which takes care of important low-level details for accurate, precise, and reproducible measurements. In particular, it makes use of cgroups, kernel namespaces, and overlay filesystems to restrict interference of the executed tool with the benchmarking host.
Microbenchmarks suite to evaluate MPI and PGAS (OpenSHMEM, UPC, and UPC++) libraries for CPUs and GPUs.
interbench is designed to benchmark interactivity on Linux. It is designed to measure the effect of changes in Linux kernel design or system configuration changes such as CPU, I/O scheduler and filesystem changes and options. With careful benchmarking, different hardware can be compared.
Benchmark is a library to benchmark code snippets, similar to unit tests.
This package provides benchmarks for implementations of the Message Passing Interface (MPI). It contains MPI performance measurements for point-to-point and global communication, and file, operations for a range of message sizes. The generated benchmark data fully characterize:
Performance of a cluster system, including node performance, network latency, and throughput;
Efficiency of the MPI implementation.
Bonnie++ is a benchmark suite that is aimed at performing a number of simple tests of hard drive and file system performance. Bonnie++ allows you to benchmark how your file systems perform with respect to data read and write speed, the number of seeks that can be performed per second, and the number of file metadata operations that can be performed per second.
BenchExec is a framework for reliable benchmarking, which takes care of important low-level details for accurate, precise, and reproducible measurements. In particular, it makes use of cgroups, kernel namespaces, and overlay filesystems to restrict interference of the executed tool with the benchmarking host.
A synthetic benchmarking tool to measure peak capabilities of OpenCL devices. It only measures the peak metrics that can be achieved using vector operations and does not represent a real-world use case.
fio is a tool that will spawn a number of threads or processes doing a particular type of I/O action as specified by the user. The typical use of fio is to write a job file matching the I/O load one wants to simulate.
KDiskMark is an HDD and SSD benchmark tool. KDiskMark abstracts away the complexity of the Flexible I/O Tester (fio) command via a convenient graphical user interface (GUI) and handles its output to provide an easy to view and interpret benchmark result. The application is written in C++ with Qt and doesn't have any runtime KDE dependencies. Among its features are:
Configurable block size, queues, and threads count for each test
Many languages support
Report generation.