Weekly Falcon/InnoDB DBT2 Overview 2008-11-28

[Hakan Kuecuekyilmaz]

Hello benchmark fans,

this weeks DBT2 runs failed on caneland, lu0009, and nehalem-1, but
succeeded on partly on walldorf. My first analyzes showed no crashes, I
think it is do to a NFS outage (walldorf runs in my living room and the
other machines are in Uppsala).

However, walldorf missed the -w100 run, because the pre-generated data
was somehow missing this time (fixed).

News for this week:
- No dramatic performance changes; all changes are in the area of noise.
- nehalem-1 runs ok but until we have a reasonable RAID setup on it
we should not consider the numbers. I just got an approval for a
softraid RAID10 setup with 6 SATA disks and I am still waiting for the
hardware to be delivered and built in.

Change set used:
revno: 2922
revision-id: hky@stripped
parent: hky@stripped
committer: Hakan Kuecuekyilmaz 
branch nick: mysql-6.0-falcon
timestamp: Thu 2008-11-27 10:22:22 +0100

caneland.mysql.com[1] numbers can be found here:
https://intranet.mysql.com/~hakank/caneland/weekly_dbt2_overview/weekly_dbt2_overview.php

lu0009.mysql.com[2] numbers can be found here:
https://intranet.mysql.com/~hakank/lu0009/weekly_dbt2_overview/weekly_dbt2_overview.php

nehalem-1.mysql.com[3] numbers can be found here:
https://intranet.mysql.com/~hakank/nehalem-1/weekly_dbt2_overview/weekly_dbt2_overview.php

walldorf@home[4] numbers can be found here:
https://intranet.mysql.com/~hakank/walldorf/weekly_dbt2_overview/weekly_dbt2_overview.php

Brief overview
****************
*** caneland ***
****************
Failure

**************
*** lu0009 ***
**************
Failure

*****************
*** nehalem-1 ***
*****************
- Please note: following nehalem-1 numbers are from a single SATA disk
setup. We will get a six disk RAID10 softraid setup soon.

Failure

****************
*** walldorf ***
****************
* -w100 missing
-w10
      -c8      -c16     -c32     -c64     -c99
F/I    67.34%   67.96%   66.05%   64.59%   62.60%

-w20
      -c8      -c16     -c32     -c64     -c128    -c192
F/I    56.43%   57.38%   59.71%   62.15%   62.16%   61.77%

-w100
      -c8      -c16     -c32     -c64     -c128    -c192    -c256    -c499
F/I     0.00%    0.00%    0.00%    0.00%    0.00%    0.00%    0.00%    0.00%


Todo:
  - Remove results from crashed runs in mean value calculation.
  - Add more information from INFORMATION_SCHEMA tables like Falcon's
  system memore usage or summary of active/pending_commit/pending_completion.
  Also talk to Ann to get more insight to Falcon metrics.
  - On walldorf put falcon_serial_log_dir to SATA disk to see
  whether the battery backed up RAID controller is the source of
  huge performance gain we saw lately.
  - (Done) Configure OProfile runs to run once per concurrency level.

Setup: datadir is on RAID10 and logdir is on separate disk (for InnoDB).

Configuration is:
MYSQLD_CONFIG_BASE="--no-defaults \
  --socket=/tmp/mysql.sock"
MYSQLD_CONFIG_GENERAL="$MYSQLD_CONFIG_BASE \
  --basedir=$FALCON \
  --datadir=$DATA_DIR \
  --tmpdir=/tmp \
  --language=${FALCON}/sql/share/english \
  --key_buffer_size=8M \
  --table_cache=4096 \
  --skip-grant-tables \
  --sort_buffer_size=2M \
  --read_buffer_size=1M \
  --tmp_table_size=67108864 \
  --thread_cache=1024 \
  --query_cache_size=0 \
  --query_cache_type=0 \
  --max_allowed_packet=512M \
  --max_connections=1601 \
  --log-error"
MYSQLD_CONFIG_FALCON="$MYSQLD_CONFIG_GENERAL \
  --skip_innodb \
  --default_storage_engine=Falcon \
  --falcon_io_threads=10 \
  --falcon_record_memory_max=650M \
  --falcon_page_cache_size=1650M \
  --falcon_page_size=8k \
  --falcon_serial_log_dir=$DATA_DIR \
  --falcon_serial_log_buffers=100 \
  --falcon_record_scavenge_threshold=70 \
  --falcon_consistent_read=off"
MYSQLD_CONFIG_INNODB="$MYSQLD_CONFIG_GENERAL \
  --skip_falcon \
  --default_storage_engine=InnoDB \
  --innodb_data_home_dir=$DATA_DIR \
  --innodb_data_file_path=ibdata1:10M:autoextend \
  --innodb_log_group_home_dir=$LOG_DIR \
  --innodb_buffer_pool_size=2300M \
  --innodb_additional_mem_pool_size=20M \
  --innodb_log_file_size=650M \
  --innodb_log_buffer_size=16M \
  --innodb_lock_wait_timeout=50 \
  --innodb_file_io_threads=10 \
  --innodb_flush_log_at_trx_commit=1 \
  --innodb_flush_method=O_DIRECT \
  --innodb_log_files_in_group=2 \
  --innodb_support_xa=0 \
  --innodb_doublewrite=0 \
  --innodb-status-file=0 \
  --skip-innodb-adaptive-hash-index \
  --innodb_max_dirty_pages_pct=70 \
  --innodb_thread_concurrency=0"


[1] caneland.mysql.com SLES10
Quad HexaCore @ 2.6GHz. Intel Xeon with 16MB L2 cache, 32GB RAM, hardware
RAID 10 on 4 x 15k RPM SAS disks.

[2] lu0009.mysql.com SLES10
Quad DualCore @ 3.4Ghz. Intel Xeon (with hyperthreading) with 16MB L2 cache, 8GB RAM,
hardware RAID 10 on 4 x 15k RPM SAS disks. This machine has inofficial Intel CPUs.

[3] nehalem-1.mysql.com Fedora Core 9
Dual DualCore @ 2.4Ghz. Intel Xeon (with SMT) with 16MB L2 cache, 16GB RAM,
Single SATA disk.

[4] walldorf@home RHEL5
Dual DualCore @ 2Ghz. Intel Xeon with 4MB L2 cache, 8GB RAM, hardware
RAID 10 on 4 x 15k RPM SAS disks.


Best regards,

Hakan

-- 
Hakan Küçükyılmaz, Senior Software Engineer DBTG/MySQL +49 160
98953296
Sun Microsystems GmbH     Sonnenallee 1, DE-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer:  Thomas Schroeder, Wolfang Engels, Dr. Roland Boemer
Vorsitz d. Aufs.rat.: Martin Haering   HRB MUC 161028     49.011, 8.376