
--+VeMz1SRxFChf6vr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/26 10:20, Barak Korren wrote:
I agree a stable distributed storage solution is the way to go if we can find one :)
=20 Distributed storages usually suffer from a large overhead because: 1. They try to be resilient to node failure, which means keeping two or more copies of the same file, which results in I/O overhead. 2. They need to coordinate metadata access for large amounts of files. Bottlenecks in the metadata management system are a common issue for distributes FS storages. =20 Since most of our data is ephemeral anyway I don't think we need to pay this overhead.
The solution for our current temporary ephemeral data would be for each node to create the vms locally, that's the scratch disks solution we started wit= h. The distributed storage would be used to store the jenkins machines templat= es, that mostly would be read by the hosts, and thus, properly cached locally w= ith a low miss rate (as they don't usually change). To actually not use at all = the central storage, whose extra levels of redundancy are only useful for more critical data (aka production datacenter machines).
=20 =20 --=20 Barak Korren bkorren@redhat.com RHEV-CI Team
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605 --+VeMz1SRxFChf6vr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXRqqdAAoJEEBxx+HSYmnDFi8IAIwiMdFKkr9PxGf9T6uYlaG7 mOgJOR2cJmOSLZ1Ysl1HZp0GxHtFqplaIv8ZUOCQ2vweRCCg75EIyCOFSBJD8aUh /ZoYxtGkQA8r3KER+XDD9uoISvjKa9Ilh/OsgQ+fvP5VpB2tI59YRCFTBS6x5mte lfWWfb5HCoVpbY7rhI+sYK4xT7YyE68PnutCOkJ/HmAFJ8p3gtW43ci70KHb5ohF 6181qkDor9ZObdulIHkIQ8lDDMFUqqnjFpIlQEXhT5qSW93wZ3dx57sm9Bi9oyuu fwmupauMWp1R8A+v/NRD/33LHd1pD4WHifOFHV0Fp0XSniTTkhFO+wcWxwypF90= =mqNm -----END PGP SIGNATURE----- --+VeMz1SRxFChf6vr--