Differences

This shows you the differences between two versions of the page.

--- rdms:webapp:processes [2025/03/20 11:02] – old revision restored (2025/03/18 10:57) wording 1 giulio
+++ rdms:webapp:processes [2025/03/24 08:46] (current) – giulio
@@ Line 1: / Line 1: @@
-====== Processes/Jobs ======
+====== Processes and Jobs ======
 {{indexmenu_n>5}}
@@ Line 43: / Line 43: @@
 {{ :rdms:webapp:rdms_procces_8.png?direct&600 |}}
-The priorities are set as such that the task that are executed from the web interface like tar creation or decompression, extraction of checksums, and the steps of the archiving workflow, are executed with a higher priority (meaning: earlier) then the automated checksum calculation. The reasons for that is that if a user uploads a folder with multiple thousand of files and the checksum calculation rules take highest priority, this might clog the whole queue for some time.
+The priorities are set such that critical tasks, tasks initiated manually by the user, and tasks that are part of a workflow are allowed to jump the queue and be executed before tasks that are not essential to the functioning of the system, numerous, common, and automatically scheduled. For example, it is important that the checksum of a file is calculated after the file is uploaded, but this calculation should not stop the archiving workflow from moving to the next step. Even if the file was uploaded way before the workflow started, the calculation of the checksum is given minimal priority, so that it may happen when the system is mostly idle.
-It is also possible to check the status of delayed rules via the CLI tool [[rdms:access:linux:icommands|iCommands]] using the `iqstat` command which shows the users delayed rules that await execution.
+You can also check the status of delayed rules via the CLI tool [[rdms:access:linux:icommands|iCommands]] using the `iqstat` command, which shows the user's delayed rules that await execution.
 {{ :rdms:webapp:rdms_procces_9.png?direct&600 |}}