Features
Spaces' issuer keys hold up at scale
A spaces token (a delegation token, credential or service auth) issued by an account on this server is now verified against the key the server already holds for it, with nothing read from the PLC directory. Other issuers' keys are used for PDS_DID_CACHE_SECS (an hour by default), then go on being used while they are read again in the background, up to the new PDS_DID_CACHE_MAX_SECS (a day by default), after which they are read again first. The server keeps up to one key for each 1 KiB of PDS_CACHE_BYTES (262,144 by default), forgetting the one used longest ago past that rather than all of them, and writes them to PDS_DATA_DIR/issuer-keys at shutdown and each minute they change, so a restart does not read every issuer's document again.
Fixes
Blobs in a bucket are read and stored over kept connections
With PDS_BLOBSTORE_S3_BUCKET set, the server keeps a connection to the store open for up to 90 seconds between requests, instead of 2, so most getBlobs and uploads no longer open a connection and do a TLS handshake first. A request that fails before any answer, as when the store closes an idle connection just as the request is sent, is sent once more over a new connection, within the same timeout.
Spaces' tokens no longer wait for the PLC directory
The key of a delegation token's, a space credential's or a revocation's issuer is kept for PDS_DID_CACHE_SECS (an hour by default) rather than five minutes. Once it is half that old, a token it verifies is answered at once and the issuer's document is read again after it, so a busy issuer's calls never wait for the directory; calls that need the same issuer's document at once share one read of it. Reads from the PLC directory now reuse an open connection instead of making a new one each time, which saves a round trip and a TLS handshake on each; posts to it still take a connection of their own.
- pds-0.7.0-x86_64-linux.tar.gz 7.5 MB
sha256:e5604e06b999 - pds-0.7.0-x86_64-linux.tar.gz.sha256 96 B
sha256:db39d523d68c