package devkit
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
Development kit - general purpose library
Install
dune-project
Dependency
Authors
Maintainers
Sources
1.20261006.tar.gz
md5=a39dbbce04bd5562a9b4443daf39c582
sha512=b10104b61384b2151521b785e7f3c3250134c75eae09b42cad69bc4a22a9a5e429beb891ee87cedf376c23d9c40f09d3f71c3fd48aa35df490c0f69dc17f3242
doc/devkit.core/Devkit_core/Memory/index.html
Module Devkit_core.MemorySource
Memory reporting - GC and OS, optionally malloc
General background:
- VSZ is not very intersting, this is the amount of memory which is mapped to the process address space. It's not really memory use, only the amount of memory the process can access without triggering a segfault.
- RSS is resident set size: this is the real world data. It's tracked by kernel and is the amount of memory currently allocated to this process. Most of the time this is what you want to look at.
- Malloc stats: those are metrics tracked by C malloc (jemalloc, tcmalloc, glibc, etc).
- size is basically like VSZ but from malloc point of view. That is it does not include mmap files for instance.
- used is basically RSS from malloc point of view.
- heap is the sum of all currently malloced values for which
freehad not been called. So this is what application requested, not including metadata, cache, etc - Gc stats are one level above and are tracked by ocaml gc. e.g. heap is the total size allocate for ocaml program. See
Gcmodule documentation for more details.
Source
type t = {rss : int;(*resident set size
*)vsize : int;(*virtual memory size
*)nr_maps : int;(*number of VM mappings
*)swap_used : int;(*used swap size
*)
} sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>