How many servers could be set in Zabbix Agent configuration file?

[ArtemD]

Hi there!
Now we are working on migration of many hosts from different "old" zabbix servers to 2 new servers (not HA) and some hosts may contain up to 6 servers in their agent's configuration file for a migration period.
Colleagues say that agent with "many" servers in config may work not properly but I couldn't find information about it.
So the question is in topic: How many servers could be set in Zabbix Agent configuration file?

[cyber]

It is not said how many...

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agentd#server

Server
A list of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies. Incoming connections will be accepted only from the hosts listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address. Note that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by RFC4291. Spaces are allowed.

and

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agentd#serveractive

ServerActive
The Zabbix server/proxy address or cluster configuration to get active checks from. The server/proxy address is an IP address or DNS name and optional port separated by colon.
Cluster configuration is one or more server addresses separated by semicolon. Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma. More than one Zabbix proxy should not be specified from each Zabbix server/cluster. If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.
Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.
If the port is not specified, default port is used.
IPv6 addresses must be enclosed in square brackets if port for that host is specified. If port is not specified, square brackets for IPv6 addresses are optional.
If this parameter is not specified, active checks are disabled.

Both of these do not say any exact number...
Server parameter just defines from where (passive) queries are accepted... you can have ranges there, it does not matter. Agent will accept a query and answers to it, it does not care what happens after that. It has given the answer and forgets it... 6,10 255... irrelevant...
ServerActive definition says "Multiple"... so I would assume, agent can keep up and send correct data to correct server... It is your job not to specify multiple proxies from one instance etc... Example there

ServerActive=zabbix.cluster.node1;zabbix.cluster.n ode2:20051,zabbix.cluster2.node1;zabbix.cluster2.n ode2,zabbix.domain

defines 3 instances... 2 which are HA and one single node instance...

Your coworkers should back their claims up with data.. I would assume having multiple servers will increase agents resource usage, but that is not "may work not properly"...

[ArtemD]

Don't know, but you can add entire subnets. For instance Server=172.19.201.0/25,172.19.223.0/24,172.19.244.0/26

I know this and using subnets instead of hostnames we could shorten the list to 4 instances.
But question was about another thing.

[cyber]

It is not said how many...

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agentd#server

Server
A list of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies. Incoming connections will be accepted only from the hosts listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address. Note that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by RFC4291. Spaces are allowed.

and

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agentd#serveractive

ServerActive
The Zabbix server/proxy address or cluster configuration to get active checks from. The server/proxy address is an IP address or DNS name and optional port separated by colon.
Cluster configuration is one or more server addresses separated by semicolon. Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma. More than one Zabbix proxy should not be specified from each Zabbix server/cluster. If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.
Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.
If the port is not specified, default port is used.
IPv6 addresses must be enclosed in square brackets if port for that host is specified. If port is not specified, square brackets for IPv6 addresses are optional.
If this parameter is not specified, active checks are disabled.

Both of these do not say any exact number...
Server parameter just defines from where (passive) queries are accepted... you can have ranges there, it does not matter. Agent will accept a query and answers to it, it does not care what happens after that. It has given the answer and forgets it... 6,10 255... irrelevant...
ServerActive definition says "Multiple"... so I would assume, agent can keep up and send correct data to correct server... It is your job not to specify multiple proxies from one instance etc... Example there

ServerActive=zabbix.cluster.node1;zabbix.cluster.n ode2:20051,zabbix.cluster2.node1;zabbix.cluster2.n ode2,zabbix.domain

defines 3 instances... 2 which are HA and one single node instance...

Your coworkers should back their claims up with data.. I would assume having multiple servers will increase agents resource usage, but that is not "may work not properly"...