MySQL Performance Blog

FreeBSD tests

Posted by Vadim @ 1:40 am :: Innodb, benchmarks, myisam, operating systems  
 Print This Post del.icio.us :: digg  
Comment RSS :: Trackback URI  

14 Comments »

1. 1. Eugene Marko

   Both servers was just cleanly installed, or something was tuned (except libthr switching)?

   Comment :: June 15, 2006 @ 5:39 am

2. 2. Vadim

   Suse is not cleanly installed, it is my everyday test server, but I did nothing special to tune it.
   FreeBSD was recompiled to support 2 CPU and with ULE scheduler.

   Comment :: June 15, 2006 @ 7:06 am

3. 3. Partha Dutta

   So out of curiosity what was the mysql configuration, and how much memory on the machine?

   Comment :: June 15, 2006 @ 7:11 am

4. 4. stanojr

   suse 10 has nptl or linuxthreads ? and what kernel version ?

   Comment :: June 15, 2006 @ 7:11 am

5. 5. Vadim

   Added more info about box and Suse

   Comment :: June 15, 2006 @ 7:22 am

6. 6. johnny

   from http://wikitest.freebsd.org/MySQL

   > There have been several reports that running with the 4BSD > scheduler offers better scheduling for MySQL workloads
   > over the ULE scheduler.

   Comment :: June 15, 2006 @ 6:49 pm

7. 7. Vadim

   Added tests ULE vs 4BSD schedulers

   Comment :: June 16, 2006 @ 2:10 am

8. 8. R_T_F_M

   Which my.cnf was used ? There is big difference between default my.cnf and my-huge.cnf when
   benchmarking with super-smack and myisam

   Comment :: August 3, 2006 @ 1:59 pm

9. 9. Vadim

   R_T_F_M,

   Yes, params inluences a lot.
   I used next configs:

   –port=3306 \
   –socket=/tmp/mysql.sock \
   –user=root $LOGERR \
   –datadir=$FSPATH \
   –basedir=$BASEPATH \
   –max_connections=3000 \
   –max_connect_errors=10 \
   –table_cache=2048 \
   –max_allowed_packet=1M \
   –binlog_cache_size=1M \
   –max_heap_table_size=64M \
   –sort_buffer_size=64K \
   –join_buffer_size=1M \
   –thread_cache=16 \
   –thread_concurrency=16 \
   –thread_stack=196K \
   –query_cache_size=0 \
   –ft_min_word_len=4 \
   –default_table_type=MYISAM \
   –transaction_isolation=REPEATABLE-READ \
   –tmp_table_size=64M \
   –skip-locking \
   –server-id=1 \
   –innodb_status_file=0 \
   –innodb_data_home_dir=$FSPATH \
   –innodb_data_file_path=ibdata1:100M:autoextend \
   –innodb_log_group_home_dir=$FSPATH \
   –innodb_buffer_pool_size=256M \
   –innodb_additional_mem_pool_size=20M \
   –innodb_log_file_size=900M \
   –innodb_log_files_in_group=2 \
   –innodb_log_buffer_size=8M \
   –innodb_flush_log_at_trx_commit=1 \
   –innodb_lock_wait_timeout=300 \
   –innodb_locks_unsafe_for_binlog=1 \
   –innodb_thread_conurrency=0

   Comment :: August 4, 2006 @ 2:19 am

10. 10. Alexander Leidinger

    What about testing 6.1 and/or the upcomming 6.2 (beta versions are available)?

    Comment :: October 21, 2006 @ 1:27 am

11. 11. Vadim

    Alexander,

    We do not use FreeBSD 6.1 and 6.2 on our servers.
    Maybe somewhen when we have access to such servers we will test it.

    Comment :: October 27, 2006 @ 9:35 am

12. 12. clipfish

    I am very disappointed, as we are using Linux and always I heard FreeBSD is more faster, more better vs..

    Comment :: April 10, 2007 @ 7:54 pm

13. 13. peter

    What to be disappointed about ? If you’re using Linux and it looks faster you should be happy with your choice

    Also there are newer versions of FreeBSD which show serious performance gains for some workloads.

    Comment :: April 11, 2007 @ 1:53 am

14. 14. james

    Look here for more info

    http://jeremy.zawodny.com/blog/archives/000697.html

    Comment :: July 14, 2007 @ 2:28 pm

Trackbacks/Pingbacks

• Interneteando » Blog Archive » MySQL en FreeBSD
  [...] (6.2), basta con cambiar la librería de threads utilizada por MySQL para que los resultados sean muy similares a los ofrecidos por una Suse y superiores a los resultados obtenidos por un linux basado en [...]