You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-user@incubator.apache.org by Mingfan Lu <mi...@gmail.com> on 2009/09/03 06:00:12 UTC
connection time out warning when testing
When I testing, there were so many warnings, most of them are "connect time
out" And I could not not pass the test for the cycle/think time are more
than target avg values.
Do you have any comment and suggestion on this ?
such as:
TimeHostLevelMessage13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12452>*UIDriverAgent[2].522.doLogin:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12453>*UIDriverAgent[10].2617.doTagSearch:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12454>*UIDriverAgent[6].1501.doTagSearch:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12455>*UIDriverAgent[12].3144.doTagSearch:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12456>*UIDriverAgent[4].1145.doEventDetail:
connect timed out13:26:11jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12457>*UIDriverAgent[5].1301.doHomePage:
connect timed out13:26:11jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12458>*UIDriverAgent[3].987.doHomePage:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12459>*UIDriverAgent[2].518.doTagSearch:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12460>*UIDriverAgent[6].1645.doEventDetail:
connect timed out13:26:11jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12461>*UIDriverAgent[14].3509.doTagSearch:
Read timed out13:26:14jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12462>*UIDriverAgent[2].594.doTagSearch:
Read timed out13:26:14jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12463>*UIDriverAgent[12].3083.doTagSearch:
Read timed out13:26:14jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12464>*UIDriverAgent[8].2142.doTagSearch:
Read timed out13:26:15jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12465>*UIDriverAgent[3].955.doTagSearch:
Read timed out13:26:15jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12466>*UIDriverAgent[5].1378.doTagSearch:
Read timed out13:26:15jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12467>*UIDriverAgent[13].3425.doTagSearch:
Read timed out13:26:15jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12468>*UIDriverAgent[0].186.doTagSearch:
Read timed out13:26:15jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12469>*UIDriverAgent[9].2401.doTagSearch:
Read timed out13:26:15jicsr116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12470>*UIDriverAgent[3].775.doTagSearch:
Read timed out13:26:16jicsr114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12471>*UIDriverAgent[2].726.doTagSearch:
Read timed out
13:26:16m116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12472>*UIDriverAgent[7].1986.doTagSearch:
Read timed out13:26:16m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12473>*UIDriverAgent[4].1165.doTagSearch:
Read timed out13:26:18m116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12474>*UIDriverAgent[5].1410.doTagSearch:
Read timed out13:26:23m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12475>*UIDriverAgent[2].735.doTagSearch:
connect timed out13:26:23m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12476>*UIDriverAgent[16].4130.doTagSearch:
connect timed out13:26:23m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12477>*UIDriverAgent[10].2733.doLogin:
connect timed out13:26:33m116WARNINGThe host jicsr117:80 (or proxy null:-1)
did not accept the connection within timeout of 5000 milliseconds13:26:33
m116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12479>*UIDriverAgent[1].278.doAddEvent:
Exception in operation.13:26:36m116WARNINGThe host jicsr117:80 (or proxy
null:-1) did not accept the connection within timeout of 5000 milliseconds
13:26:36m116WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12481>*UIDriverAgent[7].1903.doAddEvent:
Exception in operation.13:26:36m114WARNINGThe host jicsr117:80 (or proxy
null:-1) did not accept the connection within timeout of 5000 milliseconds
13:26:36m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12483>*UIDriverAgent[6].1602.doAddEvent:
Exception in operation.13:26:36m114WARNINGThe host jicsr117:80 (or proxy
null:-1) did not accept the connection within timeout of 5000 milliseconds
13:26:36m114WARNING*
exception </LogReader?runId=OlioDriver.5J&exception=12485>*UIDriverAgent[16].4230.doAddEvent:
Exception in operation.
My Configuration:
- Concurrency user: 5000
- Driver: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC: 1000Mb
- Memcached server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
NIC: 1000Mb
- Apache server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
1000Mb
==========httpd.conf=============
<IfModule prefork.c>
ListenBacklog 16384
ServerLimit 8192
MaxClients 8192
MaxRequestsPerChild 0
StartServers 128
MinSpareServers 128
MaxSpareServers 20
</IfModule>
KeepAlive On
KeepAliveTimeout 15
MaxKeepAliveRequests 1000
ExtendedStatus On
Include conf/extra/httpd-info.conf
==============================
- MYSQL server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
1000Mb; MLC SSD disk 160GB
==========my.cnf============
# The MySQL server
[mysqld]
port = 3306
socket = /opt/lamp/mysql/tmp/mysql.sock
skip-locking
key_buffer = 16M
#max_allowed_packet = 1M
max_allowed_packet = 256M
table_cache = 2048 #64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
back_log=1000
max_connections = 17000 ##10000
join_buffer_size=8M
#table_open_cache=2048
#long_query_time = 1
#log-slow-queries = /var/log/slow.log
#log-queries-not-using-indexes
wait_timeout=300
interactive_timeout=300
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Disable Federated by default
skip-federated
# Replication Master Server (default)
# binary logging is required for replication
#log-bin=mysql-bin
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /opt/lamp/mysql/var/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /opt/jiclamp/mysql/var/
innodb_log_arch_dir = /opt/jiclamp/mysql/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
innodb_buffer_pool_size = 2G
innodb_additional_mem_pool_size = 256M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 512M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50
innodb_doublewrite=0
Re: connection time out warning when testing
Posted by Akara Sucharitakul <Ak...@Sun.COM>.
Your connect timeouts cause quite a good amount of ops failures. Since
most of the requests do pass, it says that your server is doing OK
(unless you see a big drop in the throughput over time graph in the
detail results which would point to a problem at some time during the run).
In this case, it seems Apache is not accepting some connections, causing
the timeouts. Assuming your server is not overloaded, you'll need to
tune Apache and/or your network stack.
-Akara
Mingfan Lu wrote:
> This is my summary result
> Type Success
> Count Failure
> Count Mix Required Mix
> (2% deviation allowed) Pass/Fail
> HomePage 155116 146 26.1% 26.15% PASSED
> Login 61100 48 10.28% 10.22% PASSED
> TagSearch 199048 179 33.5% 33.45% PASSED
> EventDetail 146622 97 24.67% 24.68% PASSED
> PersonDetail 15524 12 2.61% 2.61% PASSED
> AddPerson 4848 160 0.82% 0.84% PASSED
> AddEvent 11977 358 2.02% 2.04% PASSED
>
>
> Response Times (seconds)
>
> Type Avg Max SD 90th% Reqd. 90th% Pass/Fail
> HomePage 0.049 42.329 0.760 0.020 1.000 PASSED
> Login 0.045 29.944 0.657 0.020 1.000 PASSED
> TagSearch 0.050 30.436 0.644 0.040 2.000 PASSED
> EventDetail 0.040 28.902 0.700 0.020 2.000 PASSED
> PersonDetail 0.036 22.970 0.608 0.020 2.000 PASSED
> AddPerson 0.387 24.119 0.976 0.440 3.000 PASSED
> AddEvent 0.398 26.626 1.116 0.460 4.000 PASSED
>
>
> Cycle/Think Times (seconds)
>
> Type Targeted Avg Actual Avg Min Max Pass/Fail
> HomePage 4.916 4.962 0.002 42.329 PASSED
> Login 4.923 4.958 0.005 30.051 PASSED
> TagSearch 4.928 4.966 0.004 30.436 PASSED
> EventDetail 4.952 4.986 0.001 33.034 PASSED
> PersonDetail 4.938 4.973 0.001 30.034 PASSED
> AddPerson 4.970 5.122 0.108 52.026 FAILED
> AddEvent 4.946 5.093 0.056 56.032 FAILED
>
>
>
>
>
> On Thu, Sep 3, 2009 at 2:00 PM, Mingfan Lu <mingfan.lu
> <http://mingfan.lu>@gmail.com <http://gmail.com>> wrote:
> >
> > When I testing, there were so many warnings, most of them are
> "connect time out" And I could not not pass the test for the cycle/think
> time are more than target avg values.
> > Do you have any comment and suggestion on this ?
> > such as:
> > Time HostLevel Message
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[2].522.doLogin: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[10].2617.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[6].1501.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[12].3144.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[4].1145.doEventDetail: connect timed out
> > 13:26:11jicsr116 WARNING
> > exception UIDriverAgent[5].1301.doHomePage: connect timed out
> > 13:26:11jicsr116 WARNING
> > exception UIDriverAgent[3].987.doHomePage: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[2].518.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[6].1645.doEventDetail: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[14].3509.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[2].594.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[12].3083.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[8].2142.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[3].955.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[5].1378.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[13].3425.doTagSearch: Read timed out
> > 13:26:15jicsr114 WARNING
> > exception UIDriverAgent[0].186.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[9].2401.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[3].775.doTagSearch: Read timed out
> > 13:26:16jicsr114 WARNING
> > exception UIDriverAgent[2].726.doTagSearch: Read timed out
> > 13:26:16m116 WARNING
> > exception UIDriverAgent[7].1986.doTagSearch: Read timed out
> > 13:26:16m114 WARNING
> > exception UIDriverAgent[4].1165.doTagSearch: Read timed out
> > 13:26:18m116 WARNING
> > exception UIDriverAgent[5].1410.doTagSearch: Read timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[2].735.doTagSearch: connect timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[16].4130.doTagSearch: connect timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[10].2733.doLogin: connect timed out
> > 13:26:33m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:33m116 WARNING
> > exception UIDriverAgent[1].278.doAddEvent: Exception in operation.
> > 13:26:36m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m116 WARNING
> > exception UIDriverAgent[7].1903.doAddEvent: Exception in operation.
> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m114 WARNING
> > exception UIDriverAgent[6].1602.doAddEvent: Exception in operation.
> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m114 WARNING
> > exception UIDriverAgent[16].4230.doAddEvent: Exception in operation.
> >
> >
> > My Configuration:
> >
> > Concurrency user: 5000
> >
> > Driver: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC: 1000Mb
> > Memcached server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
> NIC: 1000Mb
> >
> > Apache server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
> NIC: 1000Mb
> >
> > ==========httpd.conf=============
> > <IfModule prefork.c>
> > ListenBacklog 16384
> > ServerLimit 8192
> > MaxClients 8192
> > MaxRequestsPerChild 0
> > StartServers 128
> > MinSpareServers 128
> > MaxSpareServers 20
> > </IfModule>
> > KeepAlive On
> > KeepAliveTimeout 15
> > MaxKeepAliveRequests 1000
> > ExtendedStatus On
> > Include conf/extra/httpd-info.conf
> > ==============================
> >
> > MYSQL server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
> 1000Mb; MLC SSD disk 160GB
> >
> > ==========my.cnf============
> > # The MySQL server
> > [mysqld]
> > port = 3306
> > socket = /opt/lamp/mysql/tmp/mysql.sock
> > skip-locking
> > key_buffer = 16M
> > #max_allowed_packet = 1M
> > max_allowed_packet = 256M
> > table_cache = 2048 #64
> > sort_buffer_size = 512K
> > net_buffer_length = 8K
> > read_buffer_size = 256K
> > read_rnd_buffer_size = 512K
> > myisam_sort_buffer_size = 8M
> > back_log=1000
> > max_connections = 17000 ##10000
> > join_buffer_size=8M
> > #table_open_cache=2048
> > #long_query_time = 1
> > #log-slow-queries = /var/log/slow.log
> > #log-queries-not-using-indexes
> > wait_timeout=300
> > interactive_timeout=300
> >
> > # Don't listen on a TCP/IP port at all. This can be a security
> enhancement,
> > # if all processes that need to connect to mysqld run on the same host.
> > # All interaction with mysqld must be made via Unix sockets or named
> pipes.
> > # Note that using this option without enabling named pipes on Windows
> > # (via the "enable-named-pipe" option) will render mysqld useless!
> > #
> > #skip-networking
> >
> > # Disable Federated by default
> > skip-federated
> >
> > # Replication Master Server (default)
> > # binary logging is required for replication
> > #log-bin=mysql-bin
> >
> > # required unique id between 1 and 2^32 - 1
> > # defaults to 1 if master-host is not set
> > # but will not function as a master if omitted
> > server-id = 1
> >
> > # Replication Slave (comment out master section to use this)
> > #
> > # To configure this host as a replication slave, you can choose between
> > # two methods :
> > #
> > # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
> > # the syntax is:
> > #
> > # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
> > # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
> > #
> > # where you replace <host>, <user>, <password> by quoted strings and
> > # <port> by the master's port number (3306 by default).
> > #
> > # Example:
> > #
> > # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
> > # MASTER_USER='joe', MASTER_PASSWORD='secret';
> > #
> > # OR
> > #
> > # 2) Set the variables below. However, in case you choose this
> method, then
> > # start replication for the first time (even unsuccessfully, for
> example
> > # if you mistyped the password in master-password and the slave
> fails to
> > # connect), the slave will create a master.info
> <http://master.info> file, and any later
> > # change in this file to the variables' values below will be
> ignored and
> > # overridden by the content of the master.info
> <http://master.info> file, unless you shutdown
> > # the slave server, delete master.info <http://master.info> and
> restart the slaver server.
> > # For that reason, you may want to leave the lines below untouched
> > # (commented) and instead use CHANGE MASTER TO (see above)
> > #
> > # required unique id between 2 and 2^32 - 1
> > # (and different from the master)
> > # defaults to 2 if master-host is set
> > # but will not function as a slave if omitted
> > #server-id = 2
> > #
> > # The replication master for this slave - required
> > #master-host = <hostname>
> > #
> > # The username the slave will use for authentication when connecting
> > # to the master - required
> > #master-user = <username>
> > #
> > # The password the slave will authenticate with when connecting to
> > # the master - required
> > #master-password = <password>
> > #
> > # The port the master is listening on.
> > # optional - defaults to 3306
> > #master-port = <port>
> > #
> > # binary logging - not required for slaves, but recommended
> > #log-bin=mysql-bin
> >
> > # Point the following paths to different dedicated disks
> > #tmpdir = /tmp/
> > #log-update = /path-to-dedicated-directory/hostname
> >
> > # Uncomment the following if you are using BDB tables
> > #bdb_cache_size = 4M
> > #bdb_max_lock = 10000
> >
> > # Uncomment the following if you are using InnoDB tables
> > innodb_data_home_dir = /opt/lamp/mysql/var/
> > innodb_data_file_path = ibdata1:10M:autoextend
> > innodb_log_group_home_dir = /opt/jiclamp/mysql/var/
> > innodb_log_arch_dir = /opt/jiclamp/mysql/var/
> > # You can set .._buffer_pool_size up to 50 - 80 %
> > # of RAM but beware of setting memory usage too high
> > #innodb_buffer_pool_size = 16M
> > #innodb_additional_mem_pool_size = 2M
> > innodb_buffer_pool_size = 2G
> > innodb_additional_mem_pool_size = 256M
> > # Set .._log_file_size to 25 % of buffer pool size
> > innodb_log_file_size = 512M
> > innodb_log_buffer_size = 8M
> > innodb_flush_log_at_trx_commit = 2
> > innodb_lock_wait_timeout = 50
> > innodb_doublewrite=0
>
Re: connection time out warning when testing
Posted by Mingfan Lu <mi...@gmail.com>.
I have use longer rampup time (150s), so that the warning won't appear in
the steady phase And according to your nice comments, I will ignore the
warnings and failure.
Thanks again
-mingfan
On Fri, Sep 4, 2009 at 12:36 AM, Shanti Subramanyam - PAE <
Shanti.Subramanyam@sun.com> wrote:
> Regarding the cycle time failures, ignore them for now. This is a known
> issue (OLIO-81) and we're working on a fix.
>
> Shanti
>
>
> On 09/03/09 00:03, Mingfan Lu wrote:
>
>> This is my summary result
>> Type Success
>> Count Failure
>> Count Mix Required Mix
>> (2% deviation allowed) Pass/Fail
>> HomePage 155116 146 26.1% 26.15% PASSED
>> Login 61100 48 10.28% 10.22% PASSED
>> TagSearch 199048 179 33.5% 33.45% PASSED
>> EventDetail 146622 97 24.67% 24.68% PASSED
>> PersonDetail 15524 12 2.61% 2.61% PASSED
>> AddPerson 4848 160 0.82% 0.84% PASSED
>> AddEvent 11977 358 2.02% 2.04% PASSED
>>
>>
>> Response Times (seconds)
>>
>> Type Avg Max SD 90th% Reqd. 90th% Pass/Fail
>> HomePage 0.049 42.329 0.760 0.020 1.000 PASSED
>> Login 0.045 29.944 0.657 0.020 1.000 PASSED
>> TagSearch 0.050 30.436 0.644 0.040 2.000 PASSED
>> EventDetail 0.040 28.902 0.700 0.020 2.000 PASSED
>> PersonDetail 0.036 22.970 0.608 0.020 2.000 PASSED
>> AddPerson 0.387 24.119 0.976 0.440 3.000 PASSED
>> AddEvent 0.398 26.626 1.116 0.460 4.000 PASSED
>>
>>
>> Cycle/Think Times (seconds)
>>
>> Type Targeted Avg Actual Avg Min Max Pass/Fail
>> HomePage 4.916 4.962 0.002 42.329 PASSED
>> Login 4.923 4.958 0.005 30.051 PASSED
>> TagSearch 4.928 4.966 0.004 30.436 PASSED
>> EventDetail 4.952 4.986 0.001 33.034 PASSED
>> PersonDetail 4.938 4.973 0.001 30.034 PASSED
>> AddPerson 4.970 5.122 0.108 52.026 FAILED
>> AddEvent 4.946 5.093 0.056 56.032 FAILED
>>
>>
>>
>>
>>
>> On Thu, Sep 3, 2009 at 2:00 PM, Mingfan Lu <mingfan.lu <http://mingfan.lu
>> >@gmail.com <http://gmail.com>> wrote:
>> >
>> > When I testing, there were so many warnings, most of them are "connect
>> time out" And I could not not pass the test for the cycle/think time are
>> more than target avg values.
>> > Do you have any comment and suggestion on this ?
>> > such as:
>> > Time HostLevel Message
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[2].522.doLogin: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[10].2617.doTagSearch: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[6].1501.doTagSearch: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[12].3144.doTagSearch: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[4].1145.doEventDetail: connect timed out
>> > 13:26:11jicsr116 WARNING
>> > exception UIDriverAgent[5].1301.doHomePage: connect timed out
>> > 13:26:11jicsr116 WARNING
>> > exception UIDriverAgent[3].987.doHomePage: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[2].518.doTagSearch: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[6].1645.doEventDetail: connect timed out
>> > 13:26:11jicsr114 WARNING
>> > exception UIDriverAgent[14].3509.doTagSearch: Read timed out
>> > 13:26:14jicsr114 WARNING
>> > exception UIDriverAgent[2].594.doTagSearch: Read timed out
>> > 13:26:14jicsr114 WARNING
>> > exception UIDriverAgent[12].3083.doTagSearch: Read timed out
>> > 13:26:14jicsr114 WARNING
>> > exception UIDriverAgent[8].2142.doTagSearch: Read timed out
>> > 13:26:15jicsr116 WARNING
>> > exception UIDriverAgent[3].955.doTagSearch: Read timed out
>> > 13:26:15jicsr116 WARNING
>> > exception UIDriverAgent[5].1378.doTagSearch: Read timed out
>> > 13:26:15jicsr116 WARNING
>> > exception UIDriverAgent[13].3425.doTagSearch: Read timed out
>> > 13:26:15jicsr114 WARNING
>> > exception UIDriverAgent[0].186.doTagSearch: Read timed out
>> > 13:26:15jicsr116 WARNING
>> > exception UIDriverAgent[9].2401.doTagSearch: Read timed out
>> > 13:26:15jicsr116 WARNING
>> > exception UIDriverAgent[3].775.doTagSearch: Read timed out
>> > 13:26:16jicsr114 WARNING
>> > exception UIDriverAgent[2].726.doTagSearch: Read timed out
>> > 13:26:16m116 WARNING
>> > exception UIDriverAgent[7].1986.doTagSearch: Read timed out
>> > 13:26:16m114 WARNING
>> > exception UIDriverAgent[4].1165.doTagSearch: Read timed out
>> > 13:26:18m116 WARNING
>> > exception UIDriverAgent[5].1410.doTagSearch: Read timed out
>> > 13:26:23m114 WARNING
>> > exception UIDriverAgent[2].735.doTagSearch: connect timed out
>> > 13:26:23m114 WARNING
>> > exception UIDriverAgent[16].4130.doTagSearch: connect timed out
>> > 13:26:23m114 WARNING
>> > exception UIDriverAgent[10].2733.doLogin: connect timed out
>> > 13:26:33m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
>> accept the connection within timeout of 5000 milliseconds
>> > 13:26:33m116 WARNING
>> > exception UIDriverAgent[1].278.doAddEvent: Exception in operation.
>> > 13:26:36m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
>> accept the connection within timeout of 5000 milliseconds
>> > 13:26:36m116 WARNING
>> > exception UIDriverAgent[7].1903.doAddEvent: Exception in operation.
>> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
>> accept the connection within timeout of 5000 milliseconds
>> > 13:26:36m114 WARNING
>> > exception UIDriverAgent[6].1602.doAddEvent: Exception in operation.
>> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
>> accept the connection within timeout of 5000 milliseconds
>> > 13:26:36m114 WARNING
>> > exception UIDriverAgent[16].4230.doAddEvent: Exception in operation.
>> >
>> >
>> > My Configuration:
>> >
>> > Concurrency user: 5000
>> >
>> > Driver: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC: 1000Mb
>> > Memcached server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
>> NIC: 1000Mb
>> >
>> > Apache server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
>> 1000Mb
>> >
>> > ==========httpd.conf============= > <IfModule prefork.c>
>> > ListenBacklog 16384
>> > ServerLimit 8192
>> > MaxClients 8192
>> > MaxRequestsPerChild 0
>> > StartServers 128
>> > MinSpareServers 128
>> > MaxSpareServers 20
>> > </IfModule>
>> > KeepAlive On
>> > KeepAliveTimeout 15
>> > MaxKeepAliveRequests 1000
>> > ExtendedStatus On
>> > Include conf/extra/httpd-info.conf
>> > ==============================
>> >
>> > MYSQL server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
>> 1000Mb; MLC SSD disk 160GB
>> >
>> > ==========my.cnf============
>> > # The MySQL server
>> > [mysqld]
>> > port = 3306
>> > socket = /opt/lamp/mysql/tmp/mysql.sock
>> > skip-locking
>> > key_buffer = 16M
>> > #max_allowed_packet = 1M
>> > max_allowed_packet = 256M
>> > table_cache = 2048 #64
>> > sort_buffer_size = 512K
>> > net_buffer_length = 8K
>> > read_buffer_size = 256K
>> > read_rnd_buffer_size = 512K
>> > myisam_sort_buffer_size = 8M
>> > back_log=1000
>> > max_connections = 17000 ##10000
>> > join_buffer_size=8M
>> > #table_open_cache=2048
>> > #long_query_time = 1
>> > #log-slow-queries = /var/log/slow.log
>> > #log-queries-not-using-indexes
>> > wait_timeout=300
>> > interactive_timeout=300
>> >
>> > # Don't listen on a TCP/IP port at all. This can be a security
>> enhancement,
>> > # if all processes that need to connect to mysqld run on the same host.
>> > # All interaction with mysqld must be made via Unix sockets or named
>> pipes.
>> > # Note that using this option without enabling named pipes on Windows
>> > # (via the "enable-named-pipe" option) will render mysqld useless!
>> > #
>> > #skip-networking
>> >
>> > # Disable Federated by default
>> > skip-federated
>> >
>> > # Replication Master Server (default)
>> > # binary logging is required for replication
>> > #log-bin=mysql-bin
>> >
>> > # required unique id between 1 and 2^32 - 1
>> > # defaults to 1 if master-host is not set
>> > # but will not function as a master if omitted
>> > server-id = 1
>> >
>> > # Replication Slave (comment out master section to use this)
>> > #
>> > # To configure this host as a replication slave, you can choose between
>> > # two methods :
>> > #
>> > # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
>> > # the syntax is:
>> > #
>> > # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
>> > # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
>> > #
>> > # where you replace <host>, <user>, <password> by quoted strings and
>> > # <port> by the master's port number (3306 by default).
>> > #
>> > # Example:
>> > #
>> > # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
>> > # MASTER_USER='joe', MASTER_PASSWORD='secret';
>> > #
>> > # OR
>> > #
>> > # 2) Set the variables below. However, in case you choose this method,
>> then
>> > # start replication for the first time (even unsuccessfully, for
>> example
>> > # if you mistyped the password in master-password and the slave
>> fails to
>> > # connect), the slave will create a master.info <http://master.info>
>> file, and any later
>> > # change in this file to the variables' values below will be ignored
>> and
>> > # overridden by the content of the master.info <http://master.info>
>> file, unless you shutdown
>> > # the slave server, delete master.info <http://master.info> and
>> restart the slaver server.
>>
>> > # For that reason, you may want to leave the lines below untouched
>> > # (commented) and instead use CHANGE MASTER TO (see above)
>> > #
>> > # required unique id between 2 and 2^32 - 1
>> > # (and different from the master)
>> > # defaults to 2 if master-host is set
>> > # but will not function as a slave if omitted
>> > #server-id = 2
>> > #
>> > # The replication master for this slave - required
>> > #master-host = <hostname>
>> > #
>> > # The username the slave will use for authentication when connecting
>> > # to the master - required
>> > #master-user = <username>
>> > #
>> > # The password the slave will authenticate with when connecting to
>> > # the master - required
>> > #master-password = <password>
>> > #
>> > # The port the master is listening on.
>> > # optional - defaults to 3306
>> > #master-port = <port>
>> > #
>> > # binary logging - not required for slaves, but recommended
>> > #log-bin=mysql-bin
>> >
>> > # Point the following paths to different dedicated disks
>> > #tmpdir = /tmp/ > #log-update =
>> /path-to-dedicated-directory/hostname
>> >
>> > # Uncomment the following if you are using BDB tables
>> > #bdb_cache_size = 4M
>> > #bdb_max_lock = 10000
>> >
>> > # Uncomment the following if you are using InnoDB tables
>> > innodb_data_home_dir = /opt/lamp/mysql/var/
>> > innodb_data_file_path = ibdata1:10M:autoextend
>> > innodb_log_group_home_dir = /opt/jiclamp/mysql/var/
>> > innodb_log_arch_dir = /opt/jiclamp/mysql/var/
>> > # You can set .._buffer_pool_size up to 50 - 80 %
>> > # of RAM but beware of setting memory usage too high
>> > #innodb_buffer_pool_size = 16M
>> > #innodb_additional_mem_pool_size = 2M
>> > innodb_buffer_pool_size = 2G
>> > innodb_additional_mem_pool_size = 256M
>> > # Set .._log_file_size to 25 % of buffer pool size
>> > innodb_log_file_size = 512M
>> > innodb_log_buffer_size = 8M
>> > innodb_flush_log_at_trx_commit = 2
>> > innodb_lock_wait_timeout = 50
>> > innodb_doublewrite=0
>>
>>
Re: connection time out warning when testing
Posted by Shanti Subramanyam - PAE <Sh...@Sun.COM>.
Regarding the cycle time failures, ignore them for now. This is a known
issue (OLIO-81) and we're working on a fix.
Shanti
On 09/03/09 00:03, Mingfan Lu wrote:
> This is my summary result
> Type Success
> Count Failure
> Count Mix Required Mix
> (2% deviation allowed) Pass/Fail
> HomePage 155116 146 26.1% 26.15% PASSED
> Login 61100 48 10.28% 10.22% PASSED
> TagSearch 199048 179 33.5% 33.45% PASSED
> EventDetail 146622 97 24.67% 24.68% PASSED
> PersonDetail 15524 12 2.61% 2.61% PASSED
> AddPerson 4848 160 0.82% 0.84% PASSED
> AddEvent 11977 358 2.02% 2.04% PASSED
>
>
> Response Times (seconds)
>
> Type Avg Max SD 90th% Reqd. 90th% Pass/Fail
> HomePage 0.049 42.329 0.760 0.020 1.000 PASSED
> Login 0.045 29.944 0.657 0.020 1.000 PASSED
> TagSearch 0.050 30.436 0.644 0.040 2.000 PASSED
> EventDetail 0.040 28.902 0.700 0.020 2.000 PASSED
> PersonDetail 0.036 22.970 0.608 0.020 2.000 PASSED
> AddPerson 0.387 24.119 0.976 0.440 3.000 PASSED
> AddEvent 0.398 26.626 1.116 0.460 4.000 PASSED
>
>
> Cycle/Think Times (seconds)
>
> Type Targeted Avg Actual Avg Min Max Pass/Fail
> HomePage 4.916 4.962 0.002 42.329 PASSED
> Login 4.923 4.958 0.005 30.051 PASSED
> TagSearch 4.928 4.966 0.004 30.436 PASSED
> EventDetail 4.952 4.986 0.001 33.034 PASSED
> PersonDetail 4.938 4.973 0.001 30.034 PASSED
> AddPerson 4.970 5.122 0.108 52.026 FAILED
> AddEvent 4.946 5.093 0.056 56.032 FAILED
>
>
>
>
>
> On Thu, Sep 3, 2009 at 2:00 PM, Mingfan Lu <mingfan.lu
> <http://mingfan.lu>@gmail.com <http://gmail.com>> wrote:
> >
> > When I testing, there were so many warnings, most of them are
> "connect time out" And I could not not pass the test for the cycle/think
> time are more than target avg values.
> > Do you have any comment and suggestion on this ?
> > such as:
> > Time HostLevel Message
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[2].522.doLogin: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[10].2617.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[6].1501.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[12].3144.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[4].1145.doEventDetail: connect timed out
> > 13:26:11jicsr116 WARNING
> > exception UIDriverAgent[5].1301.doHomePage: connect timed out
> > 13:26:11jicsr116 WARNING
> > exception UIDriverAgent[3].987.doHomePage: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[2].518.doTagSearch: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[6].1645.doEventDetail: connect timed out
> > 13:26:11jicsr114 WARNING
> > exception UIDriverAgent[14].3509.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[2].594.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[12].3083.doTagSearch: Read timed out
> > 13:26:14jicsr114 WARNING
> > exception UIDriverAgent[8].2142.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[3].955.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[5].1378.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[13].3425.doTagSearch: Read timed out
> > 13:26:15jicsr114 WARNING
> > exception UIDriverAgent[0].186.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[9].2401.doTagSearch: Read timed out
> > 13:26:15jicsr116 WARNING
> > exception UIDriverAgent[3].775.doTagSearch: Read timed out
> > 13:26:16jicsr114 WARNING
> > exception UIDriverAgent[2].726.doTagSearch: Read timed out
> > 13:26:16m116 WARNING
> > exception UIDriverAgent[7].1986.doTagSearch: Read timed out
> > 13:26:16m114 WARNING
> > exception UIDriverAgent[4].1165.doTagSearch: Read timed out
> > 13:26:18m116 WARNING
> > exception UIDriverAgent[5].1410.doTagSearch: Read timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[2].735.doTagSearch: connect timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[16].4130.doTagSearch: connect timed out
> > 13:26:23m114 WARNING
> > exception UIDriverAgent[10].2733.doLogin: connect timed out
> > 13:26:33m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:33m116 WARNING
> > exception UIDriverAgent[1].278.doAddEvent: Exception in operation.
> > 13:26:36m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m116 WARNING
> > exception UIDriverAgent[7].1903.doAddEvent: Exception in operation.
> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m114 WARNING
> > exception UIDriverAgent[6].1602.doAddEvent: Exception in operation.
> > 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
> accept the connection within timeout of 5000 milliseconds
> > 13:26:36m114 WARNING
> > exception UIDriverAgent[16].4230.doAddEvent: Exception in operation.
> >
> >
> > My Configuration:
> >
> > Concurrency user: 5000
> >
> > Driver: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC: 1000Mb
> > Memcached server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
> NIC: 1000Mb
> >
> > Apache server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3;
> NIC: 1000Mb
> >
> > ==========httpd.conf=============
> > <IfModule prefork.c>
> > ListenBacklog 16384
> > ServerLimit 8192
> > MaxClients 8192
> > MaxRequestsPerChild 0
> > StartServers 128
> > MinSpareServers 128
> > MaxSpareServers 20
> > </IfModule>
> > KeepAlive On
> > KeepAliveTimeout 15
> > MaxKeepAliveRequests 1000
> > ExtendedStatus On
> > Include conf/extra/httpd-info.conf
> > ==============================
> >
> > MYSQL server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
> 1000Mb; MLC SSD disk 160GB
> >
> > ==========my.cnf============
> > # The MySQL server
> > [mysqld]
> > port = 3306
> > socket = /opt/lamp/mysql/tmp/mysql.sock
> > skip-locking
> > key_buffer = 16M
> > #max_allowed_packet = 1M
> > max_allowed_packet = 256M
> > table_cache = 2048 #64
> > sort_buffer_size = 512K
> > net_buffer_length = 8K
> > read_buffer_size = 256K
> > read_rnd_buffer_size = 512K
> > myisam_sort_buffer_size = 8M
> > back_log=1000
> > max_connections = 17000 ##10000
> > join_buffer_size=8M
> > #table_open_cache=2048
> > #long_query_time = 1
> > #log-slow-queries = /var/log/slow.log
> > #log-queries-not-using-indexes
> > wait_timeout=300
> > interactive_timeout=300
> >
> > # Don't listen on a TCP/IP port at all. This can be a security
> enhancement,
> > # if all processes that need to connect to mysqld run on the same host.
> > # All interaction with mysqld must be made via Unix sockets or named
> pipes.
> > # Note that using this option without enabling named pipes on Windows
> > # (via the "enable-named-pipe" option) will render mysqld useless!
> > #
> > #skip-networking
> >
> > # Disable Federated by default
> > skip-federated
> >
> > # Replication Master Server (default)
> > # binary logging is required for replication
> > #log-bin=mysql-bin
> >
> > # required unique id between 1 and 2^32 - 1
> > # defaults to 1 if master-host is not set
> > # but will not function as a master if omitted
> > server-id = 1
> >
> > # Replication Slave (comment out master section to use this)
> > #
> > # To configure this host as a replication slave, you can choose between
> > # two methods :
> > #
> > # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
> > # the syntax is:
> > #
> > # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
> > # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
> > #
> > # where you replace <host>, <user>, <password> by quoted strings and
> > # <port> by the master's port number (3306 by default).
> > #
> > # Example:
> > #
> > # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
> > # MASTER_USER='joe', MASTER_PASSWORD='secret';
> > #
> > # OR
> > #
> > # 2) Set the variables below. However, in case you choose this
> method, then
> > # start replication for the first time (even unsuccessfully, for
> example
> > # if you mistyped the password in master-password and the slave
> fails to
> > # connect), the slave will create a master.info
> <http://master.info> file, and any later
> > # change in this file to the variables' values below will be
> ignored and
> > # overridden by the content of the master.info
> <http://master.info> file, unless you shutdown
> > # the slave server, delete master.info <http://master.info> and
> restart the slaver server.
> > # For that reason, you may want to leave the lines below untouched
> > # (commented) and instead use CHANGE MASTER TO (see above)
> > #
> > # required unique id between 2 and 2^32 - 1
> > # (and different from the master)
> > # defaults to 2 if master-host is set
> > # but will not function as a slave if omitted
> > #server-id = 2
> > #
> > # The replication master for this slave - required
> > #master-host = <hostname>
> > #
> > # The username the slave will use for authentication when connecting
> > # to the master - required
> > #master-user = <username>
> > #
> > # The password the slave will authenticate with when connecting to
> > # the master - required
> > #master-password = <password>
> > #
> > # The port the master is listening on.
> > # optional - defaults to 3306
> > #master-port = <port>
> > #
> > # binary logging - not required for slaves, but recommended
> > #log-bin=mysql-bin
> >
> > # Point the following paths to different dedicated disks
> > #tmpdir = /tmp/
> > #log-update = /path-to-dedicated-directory/hostname
> >
> > # Uncomment the following if you are using BDB tables
> > #bdb_cache_size = 4M
> > #bdb_max_lock = 10000
> >
> > # Uncomment the following if you are using InnoDB tables
> > innodb_data_home_dir = /opt/lamp/mysql/var/
> > innodb_data_file_path = ibdata1:10M:autoextend
> > innodb_log_group_home_dir = /opt/jiclamp/mysql/var/
> > innodb_log_arch_dir = /opt/jiclamp/mysql/var/
> > # You can set .._buffer_pool_size up to 50 - 80 %
> > # of RAM but beware of setting memory usage too high
> > #innodb_buffer_pool_size = 16M
> > #innodb_additional_mem_pool_size = 2M
> > innodb_buffer_pool_size = 2G
> > innodb_additional_mem_pool_size = 256M
> > # Set .._log_file_size to 25 % of buffer pool size
> > innodb_log_file_size = 512M
> > innodb_log_buffer_size = 8M
> > innodb_flush_log_at_trx_commit = 2
> > innodb_lock_wait_timeout = 50
> > innodb_doublewrite=0
>
Re: connection time out warning when testing
Posted by Mingfan Lu <mi...@gmail.com>.
This is my summary result
TypeSuccess
CountFailure
CountMixRequired Mix
(2% deviation allowed)Pass/FailHomePage15511614626.1%26.15%PASSEDLogin61100
4810.28%10.22%PASSEDTagSearch19904817933.5%33.45%PASSEDEventDetail14662297
24.67%24.68%PASSEDPersonDetail15524122.61%2.61%PASSEDAddPerson48481600.82%
0.84%PASSEDAddEvent119773582.02%2.04%PASSED
Response Times (seconds)TypeAvgMaxSD90th%Reqd. 90th%Pass/FailHomePage0.049
42.3290.7600.0201.000PASSEDLogin0.04529.9440.6570.0201.000PASSEDTagSearch
0.05030.4360.6440.0402.000PASSEDEventDetail0.04028.9020.7000.0202.000PASSED
PersonDetail0.03622.9700.6080.0202.000PASSEDAddPerson0.38724.1190.9760.440
3.000PASSEDAddEvent0.39826.6261.1160.4604.000PASSED
Cycle/Think Times (seconds)TypeTargeted AvgActual AvgMinMaxPass/FailHomePage
4.9164.9620.00242.329PASSEDLogin4.9234.9580.00530.051PASSEDTagSearch4.928
4.9660.00430.436PASSEDEventDetail4.9524.9860.00133.034PASSEDPersonDetail
4.9384.9730.00130.034PASSEDAddPerson4.9705.1220.10852.026FAILEDAddEvent4.946
5.0930.05656.032FAILED
On Thu, Sep 3, 2009 at 2:00 PM, Mingfan Lu <mi...@gmail.com> wrote:
>
> When I testing, there were so many warnings, most of them are "connect
time out" And I could not not pass the test for the cycle/think time are
more than target avg values.
> Do you have any comment and suggestion on this ?
> such as:
> Time HostLevel Message
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[2].522.doLogin: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[10].2617.doTagSearch: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[6].1501.doTagSearch: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[12].3144.doTagSearch: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[4].1145.doEventDetail: connect timed out
> 13:26:11jicsr116 WARNING
> exception UIDriverAgent[5].1301.doHomePage: connect timed out
> 13:26:11jicsr116 WARNING
> exception UIDriverAgent[3].987.doHomePage: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[2].518.doTagSearch: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[6].1645.doEventDetail: connect timed out
> 13:26:11jicsr114 WARNING
> exception UIDriverAgent[14].3509.doTagSearch: Read timed out
> 13:26:14jicsr114 WARNING
> exception UIDriverAgent[2].594.doTagSearch: Read timed out
> 13:26:14jicsr114 WARNING
> exception UIDriverAgent[12].3083.doTagSearch: Read timed out
> 13:26:14jicsr114 WARNING
> exception UIDriverAgent[8].2142.doTagSearch: Read timed out
> 13:26:15jicsr116 WARNING
> exception UIDriverAgent[3].955.doTagSearch: Read timed out
> 13:26:15jicsr116 WARNING
> exception UIDriverAgent[5].1378.doTagSearch: Read timed out
> 13:26:15jicsr116 WARNING
> exception UIDriverAgent[13].3425.doTagSearch: Read timed out
> 13:26:15jicsr114 WARNING
> exception UIDriverAgent[0].186.doTagSearch: Read timed out
> 13:26:15jicsr116 WARNING
> exception UIDriverAgent[9].2401.doTagSearch: Read timed out
> 13:26:15jicsr116 WARNING
> exception UIDriverAgent[3].775.doTagSearch: Read timed out
> 13:26:16jicsr114 WARNING
> exception UIDriverAgent[2].726.doTagSearch: Read timed out
> 13:26:16m116 WARNING
> exception UIDriverAgent[7].1986.doTagSearch: Read timed out
> 13:26:16m114 WARNING
> exception UIDriverAgent[4].1165.doTagSearch: Read timed out
> 13:26:18m116 WARNING
> exception UIDriverAgent[5].1410.doTagSearch: Read timed out
> 13:26:23m114 WARNING
> exception UIDriverAgent[2].735.doTagSearch: connect timed out
> 13:26:23m114 WARNING
> exception UIDriverAgent[16].4130.doTagSearch: connect timed out
> 13:26:23m114 WARNING
> exception UIDriverAgent[10].2733.doLogin: connect timed out
> 13:26:33m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
accept the connection within timeout of 5000 milliseconds
> 13:26:33m116 WARNING
> exception UIDriverAgent[1].278.doAddEvent: Exception in operation.
> 13:26:36m116 WARNING The host jicsr117:80 (or proxy null:-1) did not
accept the connection within timeout of 5000 milliseconds
> 13:26:36m116 WARNING
> exception UIDriverAgent[7].1903.doAddEvent: Exception in operation.
> 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
accept the connection within timeout of 5000 milliseconds
> 13:26:36m114 WARNING
> exception UIDriverAgent[6].1602.doAddEvent: Exception in operation.
> 13:26:36m114 WARNING The host jicsr117:80 (or proxy null:-1) did not
accept the connection within timeout of 5000 milliseconds
> 13:26:36m114 WARNING
> exception UIDriverAgent[16].4230.doAddEvent: Exception in operation.
>
>
> My Configuration:
>
> Concurrency user: 5000
>
> Driver: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC: 1000Mb
> Memcached server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
1000Mb
>
> Apache server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
1000Mb
>
> ==========httpd.conf=============
> <IfModule prefork.c>
> ListenBacklog 16384
> ServerLimit 8192
> MaxClients 8192
> MaxRequestsPerChild 0
> StartServers 128
> MinSpareServers 128
> MaxSpareServers 20
> </IfModule>
> KeepAlive On
> KeepAliveTimeout 15
> MaxKeepAliveRequests 1000
> ExtendedStatus On
> Include conf/extra/httpd-info.conf
> ==============================
>
> MYSQL server: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz; 16G DDR3; NIC:
1000Mb; MLC SSD disk 160GB
>
> ==========my.cnf============
> # The MySQL server
> [mysqld]
> port = 3306
> socket = /opt/lamp/mysql/tmp/mysql.sock
> skip-locking
> key_buffer = 16M
> #max_allowed_packet = 1M
> max_allowed_packet = 256M
> table_cache = 2048 #64
> sort_buffer_size = 512K
> net_buffer_length = 8K
> read_buffer_size = 256K
> read_rnd_buffer_size = 512K
> myisam_sort_buffer_size = 8M
> back_log=1000
> max_connections = 17000 ##10000
> join_buffer_size=8M
> #table_open_cache=2048
> #long_query_time = 1
> #log-slow-queries = /var/log/slow.log
> #log-queries-not-using-indexes
> wait_timeout=300
> interactive_timeout=300
>
> # Don't listen on a TCP/IP port at all. This can be a security
enhancement,
> # if all processes that need to connect to mysqld run on the same host.
> # All interaction with mysqld must be made via Unix sockets or named
pipes.
> # Note that using this option without enabling named pipes on Windows
> # (via the "enable-named-pipe" option) will render mysqld useless!
> #
> #skip-networking
>
> # Disable Federated by default
> skip-federated
>
> # Replication Master Server (default)
> # binary logging is required for replication
> #log-bin=mysql-bin
>
> # required unique id between 1 and 2^32 - 1
> # defaults to 1 if master-host is not set
> # but will not function as a master if omitted
> server-id = 1
>
> # Replication Slave (comment out master section to use this)
> #
> # To configure this host as a replication slave, you can choose between
> # two methods :
> #
> # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
> # the syntax is:
> #
> # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
> # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
> #
> # where you replace <host>, <user>, <password> by quoted strings and
> # <port> by the master's port number (3306 by default).
> #
> # Example:
> #
> # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
> # MASTER_USER='joe', MASTER_PASSWORD='secret';
> #
> # OR
> #
> # 2) Set the variables below. However, in case you choose this method,
then
> # start replication for the first time (even unsuccessfully, for
example
> # if you mistyped the password in master-password and the slave fails
to
> # connect), the slave will create a master.info file, and any later
> # change in this file to the variables' values below will be ignored
and
> # overridden by the content of the master.info file, unless you
shutdown
> # the slave server, delete master.info and restart the slaver server.
> # For that reason, you may want to leave the lines below untouched
> # (commented) and instead use CHANGE MASTER TO (see above)
> #
> # required unique id between 2 and 2^32 - 1
> # (and different from the master)
> # defaults to 2 if master-host is set
> # but will not function as a slave if omitted
> #server-id = 2
> #
> # The replication master for this slave - required
> #master-host = <hostname>
> #
> # The username the slave will use for authentication when connecting
> # to the master - required
> #master-user = <username>
> #
> # The password the slave will authenticate with when connecting to
> # the master - required
> #master-password = <password>
> #
> # The port the master is listening on.
> # optional - defaults to 3306
> #master-port = <port>
> #
> # binary logging - not required for slaves, but recommended
> #log-bin=mysql-bin
>
> # Point the following paths to different dedicated disks
> #tmpdir = /tmp/
> #log-update = /path-to-dedicated-directory/hostname
>
> # Uncomment the following if you are using BDB tables
> #bdb_cache_size = 4M
> #bdb_max_lock = 10000
>
> # Uncomment the following if you are using InnoDB tables
> innodb_data_home_dir = /opt/lamp/mysql/var/
> innodb_data_file_path = ibdata1:10M:autoextend
> innodb_log_group_home_dir = /opt/jiclamp/mysql/var/
> innodb_log_arch_dir = /opt/jiclamp/mysql/var/
> # You can set .._buffer_pool_size up to 50 - 80 %
> # of RAM but beware of setting memory usage too high
> #innodb_buffer_pool_size = 16M
> #innodb_additional_mem_pool_size = 2M
> innodb_buffer_pool_size = 2G
> innodb_additional_mem_pool_size = 256M
> # Set .._log_file_size to 25 % of buffer pool size
> innodb_log_file_size = 512M
> innodb_log_buffer_size = 8M
> innodb_flush_log_at_trx_commit = 2
> innodb_lock_wait_timeout = 50
> innodb_doublewrite=0