mysql.jorge at decimal
Jul 31, 2013, 12:07 PM
Post #8 of 9
(92 views)
Permalink
|
Well,
For your storage usage anything would be fine I guess, I have on this moment
185GB :)
But your feedback is helpful, that what I had in mind, NEVER USE 5.1x
> -----Original Message-----
> From: dbmail-bounces [at] dbmail [mailto:dbmail-bounces [at] dbmail] On
> Behalf Of Reindl Harald
> Sent: quarta-feira, 31 de Julho de 2013 19:58
> To: dbmail [at] dbmail
> Subject: Re: [Dbmail] Preparing for 3.1x
>
> 5.1 had a lot of performance issues
> 5.5 was a real gain as far as i remember
>
> below my innodb-settings on 5.5, some of them make a real difference in
> performance but honestly to long ago to remember (caution: some of them
> does not exist before 5.5)
>
> the dataset is around 10 GB and compressed 8 GB on disk do *not* change
> "innodb_log_file_size" before carefully read the docs!
>
> innodb_buffer_pool_size = 5632M
> innodb_buffer_pool_instances = 6
> 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 = 0
> 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 = 1
> innodb_file_format = barracuda
> innodb_file_per_table = 1
> innodb_open_files = 600
> innodb_io_capacity = 400
> innodb_read_io_threads = 4
> innodb_write_io_threads = 4
> innodb_doublewrite = 1
> transaction-isolation = READ-COMMITTED
>
> Am 31.07.2013 20:49, schrieb Jorge Bastos:
> > Thanks for the answers,
> >
> > I said i was using 5.1x but i said it wrong, i'm using 5.0, and 3/4
> > years ago i didn't upgraded due to the slow problems on 5.1x MySQL
> version.
> >
> > So I may do a test in a clone with 5.5x when I upgrade (when 3.1.2 or
> > 3.2 is
> > out)
> >
> >> -----Original Message-----
> >> From: dbmail-bounces [at] dbmail [mailto:dbmail-bounces [at] dbmail]
> On
> >> Behalf Of Harald Leithner
> >> Sent: quarta-feira, 31 de Julho de 2013 17:33
> >> To: DBMail mailinglist
> >> Subject: Re: [Dbmail] Preparing for 3.1x
> >>
> >> Percona/MariaDB and MySQL vanilla are using the same storage engine
> >> InnoDB with some performance and feature differences.
> >>
> >> I don't have a one on one comparison, I only have read some
> benchmark
> >> where 5.5 got a huge performance boost.
> >> 5.6 should be faster but could be slower.
> >>
> >> iirc 5.6 (like Percona Server) can change indexes and some alter
> >> operations without downtime.
> >>
> >> 5.6 can start replication without downtime (not tested)
> >>
> >> I have Percona-Server-5.6.12-rc60.4 running since 2013-07-08 with 20
> >> or more piwik dbs and a daily script deleting and importing about
> 7GB.
> >>
> >> No problems.
> >>
> >> My Mailstorage runs Percona Server 5.5.31-rel30.3-520.wheezy since
> >> upgrade to DBmail 3.x, with some defect database files from mysql
> >> 5.0^^ recovered with 5.5.
> >>
> >> I'm planing to upgrade to Percona releases 5.6 when it gets stable
> >> (both webhosting and mailhosting).
> >>
> >> hope that helps
> >>
> >> Harald
> >>
> >> Am 31.07.2013, 18:04 Uhr, schrieb Jorge Bastos
> >> <mysql.jorge [at] decimal>:
> >>
> >>>> I'm on 3.1.2 using Percona MySQL Server 5.5. and if you can you
> >>>> should upgrade to MySQL 5.6 or better Percona Server 5.6 (not
> >>>> release, but I think they release the final today).
> >>>>
> >>>> And normally upgrade mysql has no downtime, even switching from
> >>>> vanilla to percona has no impact on the data structure.
> >>>>
> >>>> I haven't tested MariaDB, but I think its also binary compatible.
> >>>
> >>> I have no problem on the upgrade part, it's more a feedback from
> the
> >>> usability of 5.5 or 5.6
> >>>
> >>> I'm on InnoDB, and I'll remain on it,
> >>>
> >>> In term of speed 5.1 compared to 5.5 or 5.6, are they equal, slower
> >> or
> >>> faster?
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
|
signature.asc
