doc: more info about how to (maybe, someday) precompile mesa shader caches

This commit is contained in:
2024-12-14 07:53:11 +00:00
parent 36281a94a2
commit a105a1f028
2 changed files with 3 additions and 1 deletions

View File

@@ -49,7 +49,7 @@
- adding ~/.cache/mesa_shader_cache_db to the sandbox massively improves launch time,
probably reduces memory use,
but has unknown data leak implications.
- either (1) pre-populate the shader cache somehow
- either (1) pre-populate the shader cache somehow, e.g. <https://gitlab.freedesktop.org/mesa/shader-db>
or (2) use a seperate shader cache per-app
or (3) disable the mesa cache and see if that actually helps (MESA_SHADER_CACHE_DISABLE=true)
- sane-deadlines: show day of the week for upcoming items

View File

@@ -42,6 +42,8 @@
# - where /path/to/txt contains a list of names which represent read-only caches
# - allows to change the cache providers w/o having to update variables
#
# see also: <https://gitlab.freedesktop.org/mesa/shader-db>
# - database of common shaders (gtk4, chromium, etc) & instructions to compile for any arch
# see also: <https://github.com/ValveSoftware/Fossilize>
# which may help in generating readonly cache files
#