Comments on: FreeBSD tests

By: Interneteando » Blog Archive » MySQL en FreeBSD

Interneteando » Blog Archive » MySQL en FreeBSD — Mon, 05 Nov 2007 20:58:17 +0000

[...] (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 [...]

By: james

james — Sat, 14 Jul 2007 21:28:51 +0000

Look here for more info

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

By: peter

peter — Wed, 11 Apr 2007 08:53:19 +0000

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.

By: clipfish

clipfish — Wed, 11 Apr 2007 02:54:38 +0000

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

By: Vadim

Vadim — Fri, 27 Oct 2006 16:35:56 +0000

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.

By: Alexander Leidinger

Alexander Leidinger — Sat, 21 Oct 2006 08:27:33 +0000

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

By: Vadim

Vadim — Fri, 04 Aug 2006 09:19:42 +0000

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

By: R_T_F_M

R_T_F_M — Thu, 03 Aug 2006 20:59:45 +0000

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

By: Vadim

Vadim — Fri, 16 Jun 2006 09:10:09 +0000

Added tests ULE vs 4BSD schedulers

By: johnny

johnny — Fri, 16 Jun 2006 01:49:47 +0000

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.