Chuck1958 wrote:The default algorithm for distributing sessions is LONG (determined by the -j switch of srvctl add service) which is based on session count. The alternative is SHORT, which is either response time or throughput or CPU usage, determined by the -B switch. It sounds as though you might need
We were hoping rac would load balance for us when it was set up but we are not seeing that when during nightly batch processing one node spikes to 100% cpu and the other stays below 10. How exactly does the load balancing work? Does it consider cpu or is it purely based on the number of sessions?