data->prio_workers = 5;
- data->max_requests = 20;
data->max_client_requests = 5;
data->audit_level = 1;
if (virConfGetValueUInt(conf, "prio_workers", &data->prio_workers) < 0)
goto error;
- if (virConfGetValueUInt(conf, "max_requests", &data->max_requests) < 0)
- goto error;
if (virConfGetValueUInt(conf, "max_client_requests", &data->max_client_requests) < 0)
goto error;
unsigned int prio_workers;
- unsigned int max_requests;
unsigned int max_client_requests;
unsigned int log_level;
| int_entry "max_clients"
| int_entry "max_queued_clients"
| int_entry "max_anonymous_clients"
- | int_entry "max_requests"
| int_entry "max_client_requests"
| int_entry "prio_workers"
# (notably domainDestroy) can be executed in this pool.
#prio_workers = 5
-# Total global limit on concurrent RPC calls. Should be
-# at least as large as max_workers. Beyond this, RPC requests
-# will be read into memory and queued. This directly impacts
-# memory usage, currently each request requires 256 KB of
-# memory. So by default up to 5 MB of memory is used
-#
-# XXX this isn't actually enforced yet, only the per-client
-# limit is used so far
-#max_requests = 20
-
# Limit on concurrent requests from a single client
# connection. To avoid one client monopolizing the server
-# this should be a small fraction of the global max_requests
-# and max_workers parameter
+# this should be a small fraction of the global max_workers
+# parameter.
#max_client_requests = 5
# Same processing controls, but this time for the admin interface.
{ "min_workers" = "5" }
{ "max_workers" = "20" }
{ "prio_workers" = "5" }
- { "max_requests" = "20" }
{ "max_client_requests" = "5" }
{ "admin_min_workers" = "1" }
{ "admin_max_workers" = "5" }