Feature Description

Refering to #2258

When I check my Fiber logs, it instead of 0s now always shows: xms.
This is better, as it is more precise, but I really would recommend it, if Fiber (just like Gin) would show he smallest unit that makes sense:

• 1.423s
• 456.ms
• 18.374µs
• 432ns

Fiber, will (in my expirience) never show µs & ns, even though I am relly sure, it does not always take exactly 1ms ;)

Additional Context (optional)

The log looks like this for me (IP replaced with 123.123.123.123):

12:29:03 | 200 |     5ms |     123.123.123.123 | PUT     | /api/product/1
12:29:03 | 200 |     2ms |     123.123.123.123 | GET     | /api/products
12:29:13 | 200 |     3ms |     123.123.123.123 | GET     | /admin
12:29:13 | 304 |      0s |     123.123.123.123 | GET     | /app.min.css
12:29:13 | 200 |     1ms |     123.123.123.123 | GET     | /api/categories
12:29:13 | 200 |     2ms |     123.123.123.123 | GET     | /api/products
12:29:23 | 200 |      0s |     123.123.123.123 | GET     | /api/product/1

Also the responsetime of the very same request fluctuates between 0s and 5ms - which in my case is very high and other WebFrameworks do not do.
Since I migrate to Fiber I hope that these little things will be fixed somewhen, it is not urgent, but also the Benchmarks (where Fiber always outperforms others) are ATM not matching my real-life expirience, of beeing any faster than Gin for example.
Maybe they just apply, when a big number of requests are triggered.

Code Snippet (optional)

No response

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests may be closed without explanation.