Added comments to status documentation

These comments consolidate some clarifications made at
https://forums.foundationdb.org/t/few-queries-on-status-json/684
This commit is contained in:
tclinken 2019-12-13 15:04:02 -08:00
parent 952053ea9c
commit 74ce5988d2
1 changed files with 6 additions and 6 deletions

View File

@ -124,10 +124,10 @@
],
"command_line":"-r simulation",
"memory":{
"available_bytes":0, //an estimate of the process' fair share of the memory available to fdbservers
"available_bytes":0, // an estimate of the process' fair share of the memory available to fdbservers
"limit_bytes":0, // memory limit per process
"unused_allocated_memory":0,
"used_bytes":0
"used_bytes":0 // virtual memory size of the process
},
"messages":[
{
@ -408,18 +408,18 @@
"counter":0,
"roughness":0.0
},
"reads":{
"reads":{ // measures number of completed read requests
"hz":0.0,
"counter":0,
"roughness":0.0
},
"read_requests":{
"read_requests":{ // measures number of incoming read requests
"hz":0.0,
"counter":0,
"roughness":0.0
}
},
"bytes":{ // of operations (independent of hz). Perfectly spaced operations will have a roughness of 1.0 . Randomly spaced (Poisson-distributed) operations will have a roughness of 2.0, with increased bunching resulting in increased values. Higher roughness can result in increased latency due to increased queuing.
"bytes":{ // measures number of logical bytes read/written (ignoring replication factor and overhead on disk). Perfectly spaced operations will have a roughness of 1.0 . Randomly spaced (Poisson-distributed) operations will have a roughness of 2.0, with increased bunching resulting in increased values. Higher roughness can result in increased latency due to increased queuing.
"written":{
"hz":0.0,
"counter":0,
@ -628,7 +628,7 @@
},
"memory":{
"free_bytes":0, // an estimate of how many bytes are free to allocate to fdbservers without swapping
"committed_bytes":0,
"committed_bytes":0, // an estimate of the number of bytes of memory on the machine that are not available
"total_bytes":0 // an estimate of total physical RAM
},
"contributing_workers":4,