See please proposed changes after "!!!!" in Your config file below...
This is my opinion only, but may help...
Are Your "SLES 10 SP2 kernel version is 2.6.16.60-0.21-smp" 32-bit or 64-bit 
version?
How many DBMAIL-IMAPD processes?
 
Forgive me my poor English, please...


Date: Wed, 27 Aug 2008 13:36:00 -0500From: [EMAIL PROTECTED]: [EMAIL 
PROTECTED]: Re: [Dbmail] Query to show mailbox folders running slow
I appreciate your observations, unfortunately I am stuck with Intel Quad-Core 
processors. :)We are having significant issues handling IMAP requests in a 
timely manner (12 seconds to load the Inbox in Thunderbird and an in-house 
Java-mail app) on our dbmail implementation and I believe the problem resides 
with the database configuration.  Is there anyone out there that is running 
dbmail 2.2.10 with a MySQL 5.0.X database with a large user group that can 
share their my.cnf?  Our user count is over 4000.  This is our my.cnf:# You can 
copy this file to# /etc/my.cnf to set global options,# mysql-data-dir/my.cnf to 
set server-specific options (in this# installation this directory is 
/usr/local/mysql/data) or# ~/.my.cnf to set user-specific options.## In this 
file, you can use all long options that a program supports.# If you want to 
know which options a program supports, run the program# with the "--help" 
option.# The following options will be passed to all MySQL 
clients[client]#password       = your_passwordport            = 3306socket      
    = /var/lib/mysql/mysql.sock# Here follows entries for some specific 
programs# The MySQL server[mysqld]port                            = 3306socket  
                        = /var/lib/mysql/mysql.sockmax_connections              
   = 500max_connect_errors              = 999999 skip-lockingkey_buffer         
             = 384M
!!!! key_buffer = 1024 or 2048M
max_allowed_packet              = 8Mtable_cache                     = 
1024sort_buffer_size                = 16Mread_buffer_size                = 
16Mread_rnd_buffer_size            = 8Mmyisam_sort_buffer_size         = 
64Mthread_cache_size               = 16query_cache_size                = 
128Mquery_cache_limit               = 2Mlong_query_time                 = 10# 
These variables determine the max size of a memory temp tabletmp_table_size     
             = 32Mmax_heap_table_size             = 32Mtmpdir = /tmpdatadir = 
/var/lib/mysql# Try number of CPU's*2 for thread_concurrencythread_concurrency 
= 32
!!! TRY
!!!thread_concurrency = 8# 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# MySQL General Query Log#log=mysql.general.log# MySQL Binary 
Loglog-bin=mysql-bin#expire_logs_days       = 1 # MySQL Slow Query 
Log#log-slow-queries=/var/lib/mysql/mysql.slow.log#log-queries-not-using-indexes#
 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 omittedserver-id       = 1# InnoDB 
settingsinnodb_file_per_tableinnodb_data_home_dir            = 
/var/lib/mysql/innodb_data_file_path           = ibdata1:10M:autoextend
!!!!! Very bad! Rewrite DB file after each 1 MB increase!
!!!!! innodb_data_file_path           = ibdata1:10240M:autoextend
!!!!! this rewrite DB file after 1GB increase
!!!!! DB backup, MySQL stop, ibdata1 delete, MySQL start, data restore - long 
term process...innodb_log_group_home_dir       = 
/var/lib/mysql/innodb_log_arch_dir             = 
/var/lib/mysql/innodb_log_files_in_group       = 2innodb_buffer_pool_size       
  = 24576M
!!!! Too small! If 32GB memory, leave 2-4GB for OS, 28672M or 28G  
innodb_additional_mem_pool_size = 20Minnodb_log_file_size            = 
256Minnodb_log_buffer_size          = 16Minnodb_flush_log_at_trx_commit  = 1
!!!!innodb_flush_log_at_trx_commit  = 0innodb_lock_wait_timeout        = 
50innodb_thread_concurrency       = 1
!!!  innodb_thread_concurrency = 4 (number of cores), I 
think...innodb_thread_sleep_delay       = 0innodb_flush_method             = 
O_DIRECTtransaction-isolation           = READ-COMMITTED
!!!! One may try the lowest isolation level
!!!! transaction-isolation = READ-UNCOMMITTED
!!!! if no Java apps required... #innodb_sync_spin_loops         = 
20innodb_concurrency_tickets      = 1500 innodb_support_xa               = 
0innodb_open_files               = 
1000#skip_innodb_doublewrite#skip_innodb_checksums[mysqldump]quickmax_allowed_packet
 = 16M[mysql]no-auto-rehash# Remove the next comment character if you are not 
familiar with SQL#safe-updates[isamchk]key_buffer              = 
256Msort_buffer_size        = 256Mread_buffer             = 2Mwrite_buffer      
      = 2M[myisamchk]key_buffer              = 256Msort_buffer_size        = 
256Mread_buffer             = 2Mwrite_buffer            = 2MWe are running 
MySQL on SLES 10 SP2 kernel version is 2.6.16.60-0.21-smp 32GB of RAM on a 
4xQuad-Core Intel server.  We've changed innodb_thread_concurrency on the fly 
to see if we had any performance increase, but the latest tests show no 
improvement with decreased performance at innodb_thread_concurrency at 4 or 
higher.  I have been given until Friday (2 days) to resolve the issue before I 
am forced to go back to a flat file email system, so I greatly appreciate any 
and all help.If there are any other areas that I should be looking at, I will 
gladly take any/all suggestions.Thank you very much,Rob
On Fri, Aug 22, 2008 at 5:15 AM, Vladimir Likhachev <[EMAIL PROTECTED]> wrote:

Sorry, of course, Sun bought MySQL AB.Large server memory (more then 4 GB) 
usage details is the main reason of AMD64 usage and its suggestion by Oracle, I 
think... Not details of InnoDB format or MySQL server realisation... At whole, 
for each (heavy? strongly?) loaded server program large memory usage is very 
important.The next reason is non-independent level 2 cache memory in Intel Core 
Quad processors. Intel Em64T technology is (a very simple view) memory over 4 
GB mapping in a window 128 or 256 MB width laying below 4 GB in UMA address 
space.All this is my opinion only, based on Intel SR/SH (4*Xeon-MP) and Intel 
platforms 4*Xeon 2*Core processors, 1*Intel CoreQuad workstations usage. No use 
Intel CoreQuad for "serious" servers in companies where I work. Up to 120 GB 
InnoDB bases in DBMail 2.xx. 

Date: Fri, 22 Aug 2008 10:07:10 +1000From: [EMAIL PROTECTED]: [EMAIL 
PROTECTED]: RE: [Dbmail] Query to show mailbox folders running slow 
On Thu, 21 Aug 2008 08:01:43 +0000, Vladimir Likhachev  wrote:

> Oracle (current owner of MySQL AB) suggests AMD64 processors. Minor 
> correction. Sun bought MySQL AB. Oracle bought InnoDB. I'm not too impressed 
> with either move frankly. How many people think Oracle bought InnoDB to 
> incorporate their technology into the next version of Oracle?

Explore the seven wonders of the world Learn 
more!_______________________________________________DBmail mailing [EMAIL 
PROTECTED]://mailman.fastxs.nl/mailman/listinfo/dbmail

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to