article thumbnail

An approach to index tuning – Part 2

SQL Performance

In my last post , I started to outline the process I go through when tuning queries – specifically when I discover that I need to add a new index, or modify an existing one. His version can be used for the plan cache – the only challenge there is the information is transient, so you may not capture every query that uses a particular index.

Tuning 137
article thumbnail

An approach to index tuning – part 1

SQL Performance

A performance tuning engagement can end up taking many turns as you work through it – it all depends on what is showing up as the problem and what the data tells you. One of my favorite parts of tuning is working with indexes and, as I was thinking about this post, I was tempted to label index tuning as an "easier" task… but it really isn't.

Tuning 130
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

Migrating Netflix to GraphQL Safely

The Netflix TechBlog

The GraphQL shim enabled client engineers to move quickly onto GraphQL, figure out client-side concerns like cache normalization, experiment with different GraphQL clients, and investigate client performance without being blocked by server-side migrations. To launch Phase 1 safely, we used AB Testing.

Traffic 353
article thumbnail

PostgreSQL Connection Pooling: Part 2 – PgBouncer

Scalegrid

Once the authentication succeeds: PgBouncer checks for a cached connection, with the same username+database combination. If a cached connection is found, it returns the connection to the client. Pool definitions. The simplest definition is of the form: * = host=. Interfaces/IP:ports to listen for incoming connections.

Cache 246
article thumbnail

Impact of Querying Table Information From information_schema

Percona

having to open each table.frm (and in which my test runs, I have purposely read a very high number of tables compared to “Table-open-cache” variable). When running only sysbench, there is a high number of cache hits (~99.98%) and a low number of “misses,” which means the table_cache is big enough for the workload.

Cache 98
article thumbnail

Managing the Dynatrace API across multiple thousand environments

Dynatrace

It would definitely make my life easier! TenantCache: a cache to store tenant information and API token information and semi-permanent data to avoid unnecessary roundtrips. ? These API tokens are then stored in a local cache (the TenantCache using Redis), alongside with other rather static information of the environments: ?

Cache 235
article thumbnail

Mundane Improvements, Big Impact

Tim Kadlec

The cache hit was very low (a topic for another day), and whenever the server had to provide a fresh version of the page, it was taking an unacceptably long time more often than not. Synthetic tests, even properly tuned to match device and network characteristics, only occasionally surfaced the issue.

Tuning 69