[Pgpool-general] cont. is it expected pgpool slows down

[gurkan at resolution.com]

> > > > I have to clear out three things.
> > > > -----------------------------------------------------
> > > > 1)On our cluster we are using pgpool3.1, and testing shows that
> say
> > > logging
> > > > takes 6-10sec
> > > > without pgpool, and 30-40sec with pgpool. I have told this is not
> good
> > > eneough.
> > > > Is this difference
> > > > expected? (then I am trying to use pgpool-II to see speed
> difference)
> > > > -----------------------------------------------------
> > > 
> > > What a kind of query did you test? SELECT only?
> > Yes, login runs SELECT query.
> 
> Hmm...
> What driver did you use? JDBC or psql?
> 
> I see that your configuration is only connection pooling. Normally,
> this difference does not appear under your configuration... 
> Did you output debug log?

I am using JDBC driver for connection
(connectionURL="jdbc:edb://baba1:9999/development")
Output of debug once started is below, then did not add anything while loggin

[root at baba1 etc]# tail -f /tmp/pgpool.debug
2006-10-05 13:54:28 DEBUG: pid 14339: value: 0 kind: 2
2006-10-05 13:54:28 DEBUG: pid 14339: key: health_check_user
2006-10-05 13:54:28 DEBUG: pid 14339: value: 'nobody' kind: 4
2006-10-05 13:54:28 DEBUG: pid 14339: key: insert_lock
2006-10-05 13:54:28 DEBUG: pid 14339: value: false kind: 1
2006-10-05 13:54:28 DEBUG: pid 14339: key: ignore_leading_white_space
2006-10-05 13:54:28 DEBUG: pid 14339: value: false kind: 1
2006-10-05 13:54:28 DEBUG: pid 14339: key: log_statement
2006-10-05 13:54:28 DEBUG: pid 14339: value: true kind: 1
2006-10-05 13:54:28 DEBUG: pid 14339: weight: 1073741823

I am using pgpool for load balancing for sql queries, not for replication.
Is my config correct, for loadbalancing but no db-replication?
(tomcat points to pgpool, pgpool points to db)

----------------------------------------
#
# pgpool configuration file sample
# $Header: /cvsroot/pgpool/pgpool/pgpool.conf.sample,v 1.4 2006/02/18 13:13:37
t-ishii Exp $

# Host name or IP address to listen on: '*' for all, '' for no TCP/IP
# connections
#listen_addresses = 'localhost'
listen_addresses = 'baba1'

# Port number for pgpool
port = 9999

# Unix domain socket path.  (The Debian package defaults to
# /var/run/postgresql.)
socket_dir = '/tmp'

# Host name where PostgreSQL server is running on.  '' means localhost
# using Unix domain socket.
backend_host_name = 'baba1'

# port number PostgreSQL server is running on
backend_port = 5444

# Unix domain socket path for the backend.  (The Debian package defaults
# to /var/run/postgresql.)
backend_socket_dir = '/tmp'

# Host name where secondary PostgreSQL server is running on.  '' means
# localhost using Unix domain socket.
secondary_backend_host_name = 'baba2'

# Port number secondary PostgreSQL server is running on.  0 means no
# secondary PostgreSQL.
secondary_backend_port = 5444

# Number of pre-forked child processes
num_init_children = 32

# Number of connection pools allowed for a child process
max_pool = 20

# If idle for this many seconds, child exits.  0 means no timeout.
child_life_time = 300

# If idle for this many seconds, connection to PostgreSQL closes.
# 0 means no timeout.
connection_life_time = 0

# If child_max_connections connections were received, child exits.
# 0 means no exit.
child_max_connections = 0

# Logging directory
logdir = '/tmp'

# Replication mode
replication_mode = false
#replication_mode = true

# Set this to true if you want to avoid deadlock situations when
# replication is enabled.  There will, however, be a noticable performance
# degration.  A workaround is to set this to false and insert a /*STRICT*/
# comment at the beginning of the SQL command.
replication_strict = true

# When replication_strict is set to false, there will be a chance for
# deadlocks.  Set this to nonzero (in milliseconds) to detect this
# situation and resolve the deadlock by aborting current session.
replication_timeout = 5000

# Load balancing mode, i.e., all SELECTs except in a transaction block
# are load balanced.  This is ignored if replication_mode is false.
# load_balance_mode = false
load_balance_mode = true

# Load balance weight for master and secondary.  The actual weight is
# calculated by weight_master divided by weight_secondary.  For
# example both
#
# weight_master = 10 and weight_secondary = 5
# weight_master = 4 and weight_secondary = 2
#
# are regarded as the master having double the weight compared to the
# secondary.  Master and secondary have the same weight in the default.
weight_master = 0.5
weight_secondary = 0.5

# If there is a data mismatch between master and secondary, start
# degeneration to stop replication mode.
replication_stop_on_mismatch = false

# Semicolon separated list of queries to be issued at the end of a session
reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'

# If true print time stamp on each log line.
print_timestamp = true

# If true, operate in master/slave mode.
master_slave_mode = true

# If true, cache connection pool.
connection_cache = true

# Health check timeout.  0 means no timeout.
health_check_timeout = 20

# Health check period.  0 means no health check.
health_check_period = 0

# Health check user
health_check_user = 'nobody'

# If true, automatically lock table with INSERT statements to keep SERIAL
# data consistency.  An /*INSERT LOCK*/ comment has the same effect.  A
# /NO INSERT LOCK*/ comment disables the effect.
insert_lock = false

# If true, ignore leading white spaces of each query while pgpool judges
# whether the query is a SELECT so that it can be load balanced.  This
# is useful for certain APIs such as DBI/DBD which is known to adding an
# extra leading white space.
ignore_leading_white_space = false

# If true, print all statements to the log.  Like the log_statement option
# to PostgreSQL, this allows for observing queries without engaging in full
# debugging.
log_statement = true

-------------------------------------------------
This mail sent through IMP: www.resolution.com