Bug 8566 - Load is unfair if agents are unevenly matched
Summary: Load is unfair if agents are unevenly matched
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: ---
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks: 280
  Show dependency tree / graph
 
Reported: 2025-04-03 14:38 CEST by Samuel Mannehed
Modified: 2025-04-03 14:54 CEST (History)
0 users

See Also:
Acceptance Criteria:
MUST * It must be possible to configure different weights for different agents. * Any new configuration must be documented. SHOULD * Web Admin and tlctl should show information about differently weighted agents. * The weight configuration should be optional and shouldn't bother users who don't need it. * The weight configuration should be easy to understand at a glance. COULD * Information about differently weighted agents could only be presented if there is any weight difference in the cluster.

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Mannehed cendio 2025-04-03 14:38:37 CEST 
With the new load balancer (bug 4429) users will be evenly distributed on each agent. This is fine as long as the agents are somewhat similar resource-wise. But if one agent has half the resources of another, it is not ideal that they both could have, lets say 40 user sessions.

In some scenarios the sysadmin might want to distribute the users in a different way.
Comment 1 Samuel Mannehed cendio 2025-04-03 14:41:46 CEST 
Note that the following is currently written in the "Load balancing" section of the documentation:
> The resulting user distribution works best if the agents have similar hardware resources.
This is a reminder to update the TAG depending on the solution chosen here.
Comment 2 Samuel Mannehed cendio 2025-04-03 14:51:32 CEST 
One idea that was discussed internally was to add the possibility of specific agent weights. This would fit well into cluster.hconf, and the hostname of the agent could be the parameter-key:
> [/agents/weights]
> agent1.thinlinc.com = 50
> agent2.thinlinc.com = 200
By default, and if not specified, the weight could be 100. This number is hopefully easy to work with.
Note You need to log in before you can comment on or make changes to this bug.