Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

libcurl/performance.md: mention CA caching #496

Merged
merged 1 commit into from
Jul 31, 2024
Merged

libcurl/performance.md: mention CA caching #496

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions libcurl/performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,14 @@ your application uses connections, but if it for example iterates over N
hostnames in a short period of time, it could make sense for you to make sure
that libcurl can keep all those connections alive.

## CA store caching

For every new connection done using TLS, libcurl needs to access the CA store
to verify the remote server's certificate. If your applications do many
connections, make sure you take advantage of libcurl's CA caching so that
libcurl can avoid loading and parsing several hundred kilobytes from disk over
and over. This is however not yet supported by all TLS backends.

## make callbacks as fast as possible

In high speed data downloads, the write callback is called many times. If this
Expand Down
Loading