View Issue Details

IDProjectCategoryView StatusLast Update
0008877Talerdeployment and operationspublic2024-07-28 22:13
Reporterdvn Assigned Todvn  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status acknowledgedResolutionopen 
Target Versionpost-1.0 
Summary0008877: Make CI containers use ramdisk/tmpfs [estimate: 5h]
DescriptionIn order to lessen I/O pressure we want the CI containers to use ramdisks instead of writing to the HDD.
TagsNo tags attached.

Activities

dvn

2024-05-28 16:19

developer   ~0022482

Javier recommended passing these arguments to podman: `-d --tmpfs /tmp:rw,size=787448k,mode=1777`

dvn

2024-05-28 17:56

developer   ~0022484

The most simple and stable way to approach this is to mount a tmpfs into a path inside the container. Podman supports this natively (see previous comment).

This will require some reworking of the way we are using and managing our workspaces inside the container.

Buildbot needs to be able to setup the workspace based on the git checkout associated with a given build. Currently we mount this directory from the host into the container under /workdir. This allows buildbot on the host to manage the workspace. However, if we use a ramdisk for the workspace we will need to either copy over the mounted directory or fetch it from within the container.

Issue History

Date Modified Username Field Change
2024-05-28 16:19 dvn New Issue
2024-05-28 16:19 dvn Status new => assigned
2024-05-28 16:19 dvn Assigned To => javier.sepulveda
2024-05-28 16:19 dvn Note Added: 0022482
2024-05-28 17:56 dvn Note Added: 0022484
2024-05-29 10:56 javier.sepulveda Status assigned => acknowledged
2024-05-29 10:56 javier.sepulveda Assigned To javier.sepulveda => dvn
2024-06-24 02:49 dvn Summary Make CI containers use ramdisk/tmpfs => Make CI containers use ramdisk/tmpfs [estimate: 5h]
2024-07-28 21:49 Christian Grothoff Severity minor => feature
2024-07-28 22:13 Christian Grothoff Target Version => post-1.0