https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-07-06T08:15:45ZopenSUSE Project Management ToolopenQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2252542019-07-06T08:15:45Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>I configured openqaworker4.o.o with 350 GB instead of the default 50 GB. Monitoring.</p>
openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2266312019-07-11T10:20:37Zokurzokurz@suse.com
<ul></ul><p>filesystem ran full so I guess we need to leave some headroom. Configured for 300GB now and restarted about 300 incomplete jobs :(</p>
openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2511532019-10-18T06:33:21Zokurzokurz@suse.com
<ul></ul><p>Discussed with nsinger. We had the idea for the openqa cacheservice to dynamically look for <code>df</code> instead of a fixed space usage, e.g. use a negative number to denote who much space should be left <em>free</em> instead of how much to occupy.</p>
openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2511562019-10-18T06:55:41Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Infrastructure</i> to <i>openQA Project</i></li><li><strong>Category</strong> set to <i>Feature requests</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li></ul> openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2511682019-10-18T07:32:22Zcoolocoolo@suse.com
<ul></ul><p><em>if</em> cache would be on its own partition, it could fill it. I don't think that's generally the case</p>
openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2957472020-04-23T18:45:31Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> set to <i>future</i></li></ul> openQA Project - action #53912: Use available space for caching on each worker for increased performancehttps://progress.opensuse.org/issues/53912?journal_id=2974362020-05-01T09:31:52Zokurzokurz@suse.com
<ul></ul><p>on aarch64.o.o I increased cache limit from default 50G to 140G as I observed at a time when 16 test jobs were running in parallel and the cache had been fully used to 50G and free disk space was 307G so that we can proably increase this limit. I selected 140G for now.</p>