Remove Hardware Remove Servers Remove Traffic Remove White Paper
article thumbnail

Setting Up and Deploying PostgreSQL for High Availability

Percona

In general terms, to achieve HA in PostgreSQL, there must be: Redundancy: To ensure data redundancy and provide continuous performance when a primary server fails, multiple copies of the database reside in replica servers. When the primary server fails, a standby server takes over as the new primary.

article thumbnail

An Introduction to MySQL Replication: Exploring Different Types of MySQL Replication Solutions

Percona

In this blog post, I provide an in-depth introduction to MySQL Replication, answering what it is, how it works , its benefits and challenges, as well as reviewing some of the MySQL replication concepts that are part of the MySQL environment (and Percona Server for MySQL specifically). Set the server-id to a unique value.

Servers 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Total Cost of Ownership and the Return on Agility - All Things.

All Things Distributed

An apples to apples comparison of the costs associated with running various usage patterns on-premises and with AWS requires more than a simple comparison of hardware expense versus always-on utility pricing for compute and storage. Total Cost of Ownership. This option offers 68% savings over the on-premises option.

AWS 118
article thumbnail

Measuring Carbon is Not Enough?—?Unintended Consequences

Adrian Cockcroft

The carbon footprint of a large rack mounted server is order-of-magnitude a ton of carbon a year. A rough guide if you don’t have any better data is that with no traffic to a system it will be 10% utilization and use 30% of peak power, 25% utilization uses 50% of peak power, and at 50% utilization it uses 75% of peak power.

Energy 52
article thumbnail

MongoDB Best Practices: Security, Data Modeling, & Schema Design

Percona

It is common to see a value of “ 0″ ( or sometimes “10” ) on database servers, telling the kernel to prefer to swap to memory for better response times. 20-30% is a good general default for “dirty_ratio,” but on large-memory database servers, this can be a lot of memory.