See #931 (comment 314220)
Also, with this simple test case I get huge memleaks:...
I'm really sorry about this huge QA fail, as it's not a new problem at all.
commented on
issue #928
"Cannot compute response time for every request"
at
Knot projects / Knot Resolver
I've tested it and it seems that it is working. -> Closing
-
9588fa8a · datamodel: renamed defer section to prioritization
- ... and 1 more commit. Compare 115c11b1...9588fa8a
commented on
issue #928
"Cannot compute response time for every request"
at
Knot projects / Knot Resolver
That can still get 0, as typical resolution is just milliseconds and fully cached simple requests are commonly faster than a millisecond.