Project

Profile

Help

Task #5871

closed

Story #5762: [Epic] CI Improvements

Pursue using libeatmydata / nosync to speed up Travis

Added by mdepaulo@redhat.com over 4 years ago. Updated about 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

libeatmydata (debian family) / nosync (RH family) are LD_PRELOAD libraries that improve system disk write performance by squashing sync/fsync function calls. Thus all disk writes are cached in RAM and written to disk leisurely. They are ideal for any sort of temporary environment, like test and image building.

They are pointless when a VM's hypervisor has its virtual hard disk configured to squash sync/fsync functional calls (libvirt/kvm: "unsafe" or "writeback"), but it is unclear whether Travis does that or not with its VMs.
(Also, Travis has switched hypervisors in the past and old guidelines may no longer apply.)

We should run a test of whether Travis will benefit from libeatmydata. If it does, then methodically integrate it into tasks running directly on Travis, the containers, etc.

Actions #1

Updated by fao89 over 4 years ago

  • Tags CI/CD added
Actions #2

Updated by mdepaulo@redhat.com over 4 years ago

  • Assignee set to fao89
Actions #4

Updated by fao89 over 4 years ago

  • Status changed from NEW to POST
Actions #5

Updated by fao89 over 4 years ago

Actions #6

Updated by fao89 about 4 years ago

  • Status changed from POST to CLOSED - WONTFIX

As observed in:
https://github.com/pulp/pulpcore/pull/467
https://travis-ci.com/pulp/pulpcore/builds/144751923
libeatmydata doesn't show a significant improvement on travis runtime

Also available in: Atom PDF