Accelerate

Speed up your database queries with an automated global cache

This speed test runs a simple count query on a dataset with 500k rows and shows the results with and without the Accelerate cache.

Application
Built with Next.js (GitHub)
Deployment
Vercel Edge Functions
Database
PostgreSQL (US-EAST-1)

With Accelerate Cache

n.virginia

queries per minute

0 ms

latency

The result of the database query is cached at the Accelerate caching node in N.VIRGINIA and retrieved from there:

  • ✨ Reduced latency
  • 🚀 Increased Query Capacity
  • 🌟 Optimal Resource Utilization
Expand  to view Prisma Client query

await prisma.linkOpen.count({  cacheStrategy: { ttl: 3_600 },   where: {
    link: {
      User: {
        email: {
          contains: ".com",
        },
      },
    },
  },
});

Without Accelerate Cache

N.VIRGINIA

queries per minute

0 ms

latency

The database query and its response need to travel to the database in N.VIRGINIA and retrieved from there:

  • 🐢 High latency
  • 🪫 Low Query Capacity
  • 🚧 Poor Resource Utilization
Expand  to view Prisma Client query

await prisma.linkOpen.count({
  where: {
    link: {
      User: {
        email: {
          contains: ".com",
        },
      },
    },
  },
});

Speed test history

No tests ran yet

Database instance used

Database ProtocolInstance TypeRAMCPULocationProvider
PostgreSQLdb.m5.large8GB2 vCPUus-east-1AWS
Database Protocol

PostgreSQL

Instance Type

db.m5.large

RAM

8GB

CPU

2 vCPU

Location

us-east-1

Provider

AWS