Knowledge for our questions, fun for everyone!
Knowledge for our questions, fun for everyone!

Internal parameters

Overview
Internal parameters
Overview

Internal parameters

Load Balancer has internal parameters that defines some values for the Load Balancer’s core. this tag is named coreparams and have the following configuration options:

Option Description
threads_spawned This parameter defines the number of dispatch threads that Load Balancer will built when it is launched. The bigger the number of threads, the bigger the number of concurrent connections supported. In the test phase, a number of 10 threads support a load of about 1,000 connections per second (using httperf as traffic generator).
connection_timeout This parameter defines the interval after a connection with a server is closed due a timeout, in seconds. This parameter should be modified in function of the network delays, etc. With the server farm in a internal network, 60 seconds should be enough.
buffersize The buffer size used to share data between the client and server, measured in bytes. If you pass lots of data between the server and the client (e.g. when downloading big files) you should increment the buffersize value; else, if you have lots of small connections, you should decremente the buffersize. Note that you have a buffer per thread spawned, so be conservative with this value (if you have lots of free memory, incrementing this value should increment Load Balancers’ perfomance.
log The type of the log that Load Balancer’s will use. You can choose between the following values:
  • STDERR: dump all the log data to the standard error channel.
  • SYSLOG: dump all the log data to the syslog system facility.
  • filename: dump all the log data to the file called ’filename’.
If log property is not defined, Load Balancer won’t log data. This increment the perfomance of Load Balancer, but you can’t see nothing about its internal working. This option is useful when you have Load Balancer in a production state.
proxy_plugin This is the path to the plugin (module), that does the proxy function inside the Load Balancer. Also you can specify the plugin’s filename only (without path) if you have the module installed in the same directory that Load Balancer.
chooser_plugin this is the path to the plugin (module), that does the chooser function inside the Load Balancer. Also you can specify the plugin’s filename only (without path) if you have the module installed in the same directory that Load Balancer.

Sample


  <coreparams 
              threads_spawned="10"  
              connection_timeout="60"
              buffersize="65536" 
              log="loadb.log"
              type="TCP"
              proxy_plugin="proxyplugin_http.so"
              chooser_plugin="chooser_bf.so"
   />

Proxy & chooser configuration

These two plugins don’t have configuration parameters, but in the future, maybe they need some, so they have room in the configuration for this configuration. You must have the configuration tag entries for these two plugins in the file, without parameters:


  <proxy_plugin/>
  <chooser_plugin/>

Published at 18/09/2003 21:43:33
Last Updated 08/12/2003 20:25:07
By Juan M. Casillas




Google



Internal parameters
Overview

Sections
Load Balancer

February's articles
S M T W T F S
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
      
More articles

Search


Other versions
XML version
Printable version

Download
Latest version is 0.5 (28.8 Kb, tar.gz file)

 » from JMCResearch
Quick links
Install HOW-TO
Local CVS Repository
Ask your questions