Slide 1

Zarafa in larger environments

Michael Kromer & Mark Sartor

MySQL

InnoDB Buffer Pool

InnoDB bufferpool is useful for:

Read Cache

Write Cache (dirty pages)

InnoDB Buffer Pool

InnoDB is flushing dirty pages to disk:

When MySQL is idle

When max_dirty_pages_pct value has been reached

When transaction logs are full

InnoDB Buffer Pool

Example:

innodb_buffer_pool_size = 4G

innodb_log_file_size = 1G

innodb_log_files_in_group = 3

Means:

Total Read + Write cache = 4G

Total Transaction Logs = 3G

max_dirty_pages_pct defaults to 90% of bufferpool = 3.6G

InnoDB Buffer Pool

Total Read + Write cache = 4G

Total Transaction Logs = 3G

max_dirty_pages_pct defaults to 90% of bufferpool = 3.6G

At high MySQL workload the read cache will not be more than: 1G

InnoDB Buffer Pool

InnoDB Buffer Pool

MySQL Storage

Low Latency Storage

Hybrid Storage

Use mysqltuner(.pl)

MySQL backups

Reverse Proxy

ZCP 7.1 has new functionality to make simplify the architecture for a

ZCP MultiServer cluster behind a reverse proxy.

Reverse Proxy

Reverse Proxy

Reverse Proxy

General Recommendations I

Use modern kernels [cgroups]

NFS Locking

Mail Routing Optimization [LDAP]

Antivirus Handling

Redirection Zarafa Node

Use modern MySQL

Move softdelete mechanism to nightly process

Apache Tuning

General Recommendations II

LDAP Optimization (indexing + caching)

LDAP failover feature (ZCP 7.1)

LACP / Channel Bonding (802.3ad)

Virtualization: Use persistent memory reservation

Virtualization: Use PARAvirt-stuff!

Linux optimization basics (noatime, etc.)

Z-push 2 (sink)