Remove 2007 Remove Cache Remove Scalability Remove Servers
article thumbnail

InnoDB Performance Optimization Basics

Percona

This blog is in reference to our previous ones for ‘Innodb Performance Optimizations Basics’ 2007 and 2013. Hardware Memory The amount of RAM to be provisioned for database servers can vary greatly depending on the size of the database and the specific requirements of the company. Benchmark before you decide.

article thumbnail

A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications

All Things Distributed

We were pushing the limits of what was a leading commercial database at the time and were unable to sustain the availability, scalability and performance needs that our growing Amazon business demanded. We had an advanced team of database administrators and access to top experts within Oracle. million requests per second.

Internet 128
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

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

Egnyte is a secure Content Collaboration and Data Governance platform, founded in 2007 when Google drive wasn't born and AWS S3 was cost-prohibitive. Edge caching. In general, Egnyte connect architecture shards and caches data at different levels based on: Amount of data. Application Servers. Nginx for disk based caching.

article thumbnail

How To Measure the Working Set Size on Linux

Brendan Gregg

It is used for capacity planning and scalability analysis. Here is a MySQL database server (mysqld), PID 423, and measuring its working set size for 0.1 Short durations can be useful for understanding how well a WSS will fit into the CPU caches (L1/L2/L3, TLB L1/L2, etc). That's the working set size. 16.570 403.66 32.980 403.66

Cache 71
article thumbnail

How To Measure the Working Set Size on Linux

Brendan Gregg

It is used for capacity planning and scalability analysis. Here is a MySQL database server (mysqld), PID 423, and measuring its working set size for 0.1 Short durations can be useful for understanding how well a WSS will fit into the CPU caches (L1/L2/L3, TLB L1/L2, etc). That's the working set size. 16.570 403.66 32.980 403.66

Cache 40