From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Max Carrara <m.carrara@proxmox.com>
Subject: Re: [pbs-devel] RFC: Scheduler for PBS
Date: Fri, 9 Aug 2024 14:52:56 +0200 [thread overview]
Message-ID: <ff31232c-7f29-4859-9204-6c579b2ef7a5@proxmox.com> (raw)
In-Reply-To: <D3B9YIIHKRP2.2EX6MKWE3C0NP@proxmox.com>
Hi,
great to see that you tackle this!
I read through the overview, which sounds fine, but I think that it
should more reflect the actual issues, namely limitations in memory,
threads, disk io and network.
The actual reason people want to schedule things is to not overload the system
(because of timeouts, hangs, etc.) so any scheduling system should consider
not only the amount of jobs, but how much resources the the job will/can
utilize.
E.g. when I tried to introduce multi-threaded tape backup (configurable threads
per tape job), Thomas rightfully said that it's probably not a good idea, since
making multiple parallel tape backup job increases the load by much more than before.
I generally like the approach, but I personally would like to see some
work with resource constraints, for example one could imagine a configurable
amount of available threads and (configurable?) used thread by job type
so i can set my available to e.g. 10 and if my tape backup jobs then get
4, i can start 2 in parallel but not more
Such a system does not have to be included from the beginning IMO, but the
architecture should be prepared for such things
Does that make sense?
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-08-09 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 9:31 Max Carrara
2024-08-09 11:22 ` Christian Ebner
2024-08-09 12:33 ` Max Carrara
2024-08-09 12:52 ` Dominik Csapak [this message]
2024-08-09 14:20 ` Max Carrara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff31232c-7f29-4859-9204-6c579b2ef7a5@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=m.carrara@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox