Experience Report for Feature Request
What you wanted to do
Have a quick and easy reading of the Live and Bulk loaders logs.
Why that wasn’t great, with examples
For those who are already used to it, reading live and bulk logs is fine. However, it can be confusing sometimes. And whoever is arriving now to Dgraph, will remain confused for a while.
This log is too long - I suggest to change it from:
N-Quads/s [last 5s]: 398000
to
N-Quads/5s: 398000
Also, add a “pipe” character to make a logical visual separation. Because some users may think that a specific value is related to another legend.
Something like this would be great visually
Elapsed: 01m35s | Txns: 2000 | N-Quads: 20000000 | N-Quads/5s: 398000 | Aborts: 0
Elapsed: 01m35s | Txns: 2000 | N-Quads: 20000000 | N-Quads/5s: 398000 | Aborts: 0
Elapsed: 01m35s | Txns: 2000 | N-Quads: 20000000 | N-Quads/5s: 398000 | Aborts: 0
Also, would be very nice to have dot separation in large numbers.
Elapsed: 01m35s | Txns: 2.000 | N-Quads: 20.000.000 | N-Quads/5s: 398.000 | Aborts: 0
Also, optionally, have a unit prefix.
Elapsed: 01m35s | Txns: 2k | N-Quads: 20.3M | N-Quads/5s: 398k | Aborts: 0
Any external references to support your case
I have mentioned this to @ashishgoswami.
Another point to mention is that the terminology N-Quads is different from what it means in W3C docs references. So in the logs, it should be N-Triples. See Increase RDF compliance support (N-Triples).
e.g:
Elapsed: 01m35s | Txns: 2.000 | N-Triples: 20.000.000 | N-Triples/5s: 398.000 | Aborts: 0
Elapsed: 01m35s | Txns: 2.000 | N-Triples: 20.000.000 | N-Triples/5s: 398.000 | Aborts: 0
Elapsed: 01m35s | Txns: 2.000 | N-Triples: 20.000.000 | N-Triples/5s: 398.000 | Aborts: 0