6
66%
master: 66%

Ran 26 Apr 2019 06:09PM UTC

Files 93

Run time 5s

Badge

Embed ▾

Committed 26 Apr 2019 05:53PM UTC coverage: 60.935% (-0.2%) from 61.121%

Job # RUN="coverage" CONTAINER="netaccess"

Build Type

push

travis-ci

Committed by

rolandshoemaker

Commit Message

sa: use a faster query for certificates per name rate limit (#4179)

Right now we run a `SELECT COUNT` query on issuedNames to calculate this rate limit.
Unfortunately, counting large numbers of rows is very slow. This change introduces a
dedicated table for keeping track of that rate limit.

Instead of being keyed by FQDN, this new `certificatesPerName` table is keyed by
the same field as rate limits are calculated on: the base domain. Each row has a base
domain, a time (chunked by hour), and a count. This means calculating the rate limit
status for each domain reads at most 7 * 24 rows.

This should particularly speed up cases when a single domain has lots of subdomains.

Fixes #4152

Run Details

11070 of 18167 relevant lines covered (60.93%)

0.68 hits per line

letsencrypt / boulder / 10520 / 6
66%
master: 66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10520.6 (RUN="coverage" CONTAINER="netaccess")

letsencrypt / boulder / 10520 / 6 66% master: 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10520.6 (RUN="coverage" CONTAINER="netaccess")

letsencrypt / boulder / 10520 / 6
66%
master: 66%

README BADGES
x