Artifactspublic-v0

curl

master
ply4 git calls193 ms288 KiB2 cachedprotocol v2
75 lines1.9 KiBRaw

NAME

CURLMOPT_RESOLVE_THREADS_MAX - max threads for threaded DNS resolver

SYNOPSIS

c
#include <curl/curl.h>

CURLMcode curl_multi_setopt(CURLM *handle, CURLMOPT_RESOLVE_THREADS_MAX,
                            long amount);

DESCRIPTION

Pass a long for the amount. The set number is used as the maximum number of threads to be used for the threaded DNS resolver. It has to be a positive number in the range of 32 bits.

When libcurl is built with a threaded resolver, which is the default on many systems, it uses a thread pool to lookup addresses and other properties of hostnames so other transfers are not blocked by this.

Threads are started on demand to perform the resolving and shut down again after a period of inactivity. When the maximum number of threads is reached, outstanding resolves are held in a queue and served when a thread becomes available.

The default maximum is expected to work fine for many situations. Application may override it using this option for the multi handle.

Changing this value while there are resolves in progress is possible. Increasing the value takes effect right away. Lowering the value does not close down any resolves, but ends threads above the new maximum once the resolving is done.

DEFAULT

20.

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURLM *m = curl_multi_init();
  /* never use more than 5 threads for resolving */
  curl_multi_setopt(m, CURLMOPT_RESOLVE_THREADS_MAX, 5L);
}

%AVAILABILITY%

RETURN VALUE

curl_multi_setopt(3) returns a CURLMcode indicating success or error.

CURLM_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3).

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: CURLMOPT_RESOLVE_THREADS_MAX
5Section: 3
6Source: libcurl
7See-also:
8 - CURLOPT_IPRESOLVE (3)
9 - CURLOPT_RESOLVE (3)
10Protocol:
11 - All
12Added-in: 8.20.0
13---
15# NAME
17CURLMOPT_RESOLVE_THREADS_MAX - max threads for threaded DNS resolver
19# SYNOPSIS
21~~~c
22#include <curl/curl.h>
24CURLMcode curl_multi_setopt(CURLM *handle, CURLMOPT_RESOLVE_THREADS_MAX,
25 long amount);
26~~~
28# DESCRIPTION
30Pass a long for the **amount**. The set number is used as the maximum number
31of threads to be used for the threaded DNS resolver. It has to be a
32positive number in the range of 32 bits.
34When libcurl is built with a threaded resolver, which is the default on
35many systems, it uses a thread pool to lookup addresses and other
36properties of hostnames so other transfers are not blocked by this.
38Threads are started on demand to perform the resolving and shut down
39again after a period of inactivity. When the maximum number of threads
40is reached, outstanding resolves are held in a queue and served when
41a thread becomes available.
43The default maximum is expected to work fine for many situations. Application
44may override it using this option for the multi handle.
46Changing this value while there are resolves in progress is possible.
47Increasing the value takes effect right away. Lowering the value does
48not close down any resolves, but ends threads above the new maximum
49once the resolving is done.
51# DEFAULT
5320.
55# %PROTOCOLS%
57# EXAMPLE
59~~~c
60int main(void)
62 CURLM *m = curl_multi_init();
63 /* never use more than 5 threads for resolving */
64 curl_multi_setopt(m, CURLMOPT_RESOLVE_THREADS_MAX, 5L);
66~~~
68# %AVAILABILITY%
70# RETURN VALUE
72curl_multi_setopt(3) returns a CURLMcode indicating success or error.
74CURLM_OK (0) means everything was OK, non-zero means an error occurred, see
75libcurl-errors(3).
Diagnostics4 git calls · 193 ms
CallStatusSizeTime0193 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=188
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.1 KiB188 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1079
git.response.cache=MISS
git.response.duration_ms=188
git.fetch.wants=593ff7fa02ec27ebe927058a9b98948e0cfd9544
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1079
git.pkt.payload.max=1058
git.sideband.band1.bytes=1057
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e37eec18009318
Request
bc629060…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format