headers
ITronic Harald Leithner | 13 Jun 2012 10:16
Picon
Favicon

Re: MySQL 5.0 vs 5.5

Hi Jorge,

I upgraded form dbmail 2.2 to 3.0 and mysql 5.0 to percona server 5.5 but  
on a new hardware so I couldn't give you any good information about  
performance but I think Reindl Harald may have some information about the  
innodb compressed feature in mysql 5.5.

regards,

Harald Leithner

Am 13.06.2012, 00:52 Uhr, schrieb Jorge Bastos <mysql.jorge <at> decimal.pt>:

> Howdy,
>
>
> I'd like to collect some stats about MySQL versions.
>
>
> Is there anyone who moved from MySQL 5.0 to 5.5 with 3.0x version?
>
> Is there any performance impact? (5.1 has some performance problems)
>
>
> Thanks in advanced,
>
> Jorge,
Permalink | Reply |
headers
Reindl Harald | 13 Jun 2012 11:05
Favicon

Re: MySQL 5.0 vs 5.5


Am 13.06.2012 10:16, schrieb ITronic Harald Leithner:
> Hi Jorge,
> 
> I upgraded form dbmail 2.2 to 3.0 and mysql 5.0 to percona server 5.5 but on a new hardware so I couldn't give you
> any good information about performance but I think Reindl Harald may have some information about the innodb
> compressed feature in mysql 5.5

these are my innodb-settings with MySQL 5.5 on a machine
with 9500 MB RAM (VMware ESXi) and around 8.75 GB messages
reduced to 6.51 due compressed tables

these settings combined with upgrade to 5.5 made
our dbmail setup much faster as before

we are using compressed tables since 2009 / MySQL 5.1
in 5.1 you needed innodb_plugin, 5.5 supports native

be aware you need "innodb_file_per_table" for this feature

innodb_buffer_pool_size                 = 3072M
innodb_buffer_pool_instances            = 3
innodb_purge_threads                    = 1
innodb_max_purge_lag                    = 200000
innodb_max_dirty_pages_pct              = 60
innodb_additional_mem_pool_size         = 64M
innodb_log_file_size                    = 512M
innodb_log_buffer_size                  = 256M
innodb_thread_concurrency               = 32
innodb_thread_sleep_delay               = 10
(Continue reading)

Permalink | Reply |
headers
Jorge Bastos | 13 Jun 2012 22:23
Picon

Re: MySQL 5.0 vs 5.5

Hi Both,

Thanks for your feedback's!

Jorge,

> -----Original Message-----
> From: dbmail-bounces <at> dbmail.org [mailto:dbmail-bounces <at> dbmail.org] On
> Behalf Of Reindl Harald
> Sent: quarta-feira, 13 de Junho de 2012 10:05
> To: dbmail <at> dbmail.org
> Subject: Re: [Dbmail] MySQL 5.0 vs 5.5
> 
> 
> 
> Am 13.06.2012 10:16, schrieb ITronic Harald Leithner:
> > Hi Jorge,
> >
> > I upgraded form dbmail 2.2 to 3.0 and mysql 5.0 to percona server 5.5
> > but on a new hardware so I couldn't give you any good information
> > about performance but I think Reindl Harald may have some information
> > about the innodb compressed feature in mysql 5.5
> 
> these are my innodb-settings with MySQL 5.5 on a machine with 9500 MB
> RAM (VMware ESXi) and around 8.75 GB messages reduced to 6.51 due
> compressed tables
> 
> these settings combined with upgrade to 5.5 made our dbmail setup much
> faster as before
>
(Continue reading)

Permalink | Reply |
headers
Jorge Bastos | 13 Jun 2012 23:51
Picon

Re: MySQL 5.0 vs 5.5

One extra info, for both,

Wich are the DB size each of you have?
I have 120GB now, InnoDB, with file_per_table.

Jorge,s

> we are using compressed tables since 2009 / MySQL 5.1 in 5.1 you needed
> innodb_plugin, 5.5 supports native
> 
> be aware you need "innodb_file_per_table" for this feature
> 
> innodb_buffer_pool_size                 = 3072M
> innodb_buffer_pool_instances            = 3
> innodb_purge_threads                    = 1
> innodb_max_purge_lag                    = 200000
> innodb_max_dirty_pages_pct              = 60
> innodb_additional_mem_pool_size         = 64M
> innodb_log_file_size                    = 512M
> innodb_log_buffer_size                  = 256M
> innodb_thread_concurrency               = 32
> innodb_thread_sleep_delay               = 10
> innodb_flush_log_at_trx_commit          = 2
> innodb_support_xa                       = 1
> innodb_lock_wait_timeout                = 50
> innodb_table_locks                      = 0
> innodb_checksums                        = 0
> innodb_file_format                      = barracuda
> innodb_file_per_table                   = 1
> innodb_open_files                       = 600
(Continue reading)

Permalink | Reply |

Gmane