Bug 48728 - Switching between computer rooms in the UMC is very slow
Switching between computer rooms in the UMC is very slow
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: iTALC
UCS@school 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-21 17:56 CET by Nico Stöckigt
Modified: 2023-10-26 12:28 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019022021000447
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2019-02-21 17:56:54 CET
When switching from one computerroom to another it might take a quite long time. This is probably due to a hardcoded timeout - in this case 1 sec. It figures out that, when leaving a computerroom, for each computer in the room, whether or not it's online, the connection is closed but in case there is no connection it is waited until the configured timeout. So for each offline computer it took at least 1 sec which can accumulate to a decent amount of time to wait.

Wouldn't it be better if the "shutdown" is done in parallel rather then serial or at least offline computers are just skipped?
Comment 1 Florian Best univentionstaff 2021-09-20 15:31:37 CEST
Does this apply to Veyon as well? Then please change the component.
Comment 2 Jan-Luca Kiok univentionstaff 2023-10-26 12:28:53 CEST
This issue has been filed against UCS@school 4.3.

UCS@school 4.3 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.