Feature #5630: Reproducible builds
Better balance our isobuilders' I/O load over all available SSDs
They hit almost exclusively md1. I want their load to be better spread over md1 and md3, at least for their
-data and their
-libvirt volumes, like I did for isotesters already. I'll take care of it myself as it seems I'm the one who cares most about this topic.
#1 Updated by intrigeri about 1 year ago
- Subject changed from Better spread our isobuilders' I/O over available SSDs to Better balance our isobuilders' I/O load over all available SSDs
- Status changed from Confirmed to Resolved
- Assignee deleted (
- % Done changed from 0 to 100
First, I've deleted isotesters 7 and 8 (that have been off for a long time anyway) and the corresponding LVs in order to have some margin to work with. Then I've moved some unrelated stuff around to make some more room where I needed it, and finally:
isotester*-datato have 3 of them on md1 and the 3 others on md3
isobuilder*-datato have 2 of them on md1 and the 2 others on md3
So calling this done.
Next time we need more space on SSDs, we could consider moving some system LVs to rotating drives: we'll make boot performance a bit worse, but once services are started the system partition shouldn't be heavily accessed. But I'll want to check Munin first to ensure our rotating drives are not I/O-saturated already.