Product specifications

• available memory is the difference between max memory and the current amount of allocated
memory
• constant is the maximum HEALTH (set to 10000 for Connection Server).
4.5.2 Load balancing logic
1.
Each candidate server reports its HEALTH to the load balancer.
A candidate server is a Connection Server server that supports the requested network layer and
database pair. Assuming that all the server instances support the same set of data sources, they
are all potential candidates for serving a client request.
2.
The load balancer determines which server to send the client request to by identifying and ranking
the healthiest servers. It then identifies the best server among those. If the set of servers only contains
one server, then this is the target server.
Note:
The HEALTH is updated during the lifecycle of the server. HEALTH is recalculated when:
• a job is created or destroyed
• a job is prepared or executed
• a data fetch operation is performed
4.5.3 Backward compatibility
The load-balancing mechanism is supported on all platforms starting from the SAP BusinessObjects
Business Intelligence platform 4.0 Feature Pack 3 release. In the case of incremental deployments or
limited upgrades on previous releases, backward compatibility is supported. Any server which fails to
report its HEALTH to the load balancer is considered as healthy, that is, at its maximum health.
Note:
Load balancing is also available for some platforms in some Service Packs of previous releases. Contact
your SAP representative for more information.
4.6 Memory allocation
The Native Connectivity Service can use the HOARD memory-allocation functionality on 64-bit MS
Windows. HOARD is a scalable and optimized memory allocator for C++ components that allows the
service to have better performance, better scalability, and less memory fragmentation.
2012-03-1534
Learning data access specifics