Improve tests performance by moving /tmp on tmpfs

Bug #1205393 reported by Alexei Kornienko
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure

Bug Description

Some tests actively use /tmp directory to create test fixtures, db files, etc (ceilometer for example creates MongoDB database files in /tmp). We could improve tests performance if we'll move /tmp on tmpfs

Revision history for this message
Jeremy Stanley (fungi) wrote :

Before doing this, we'll want to characterize the state of /tmp utilization on the current slaves and also reevaluate swap allocation (I generally recommend increasing swap space by the size of any new tmpfs filesystems as a safety net against OOM conditions from excess data written there).

Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Clark Boylan (cboylan) wrote :

I think a better approach may be to run testr under eatmydata. Then we don't have to maintain state on the slaves themselves, instead individual projects can make use of the less reliable but speedier IO. This may not give us all of the speedup that a tmpfs would, but it should be much easier to manage.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.