|
2024-01-14
| ||
| 13:33 | • Ticket [316edadc24] Add a cache in OFDNSResolver status still Fixed with 3 other changes artifact: 377a0f9faf user: js | |
|
2023-12-29
| ||
| 16:30 | • Fixed ticket [316edadc24]. artifact: 911cb9ad04 user: js | |
|
2023-07-15
| ||
| 14:39 | • Ticket [316edadc24]: 4 changes artifact: ac9c40eb73 user: js | |
|
2022-11-28
| ||
| 22:15 | • Ticket [316edadc24]: 5 changes artifact: c92fe9eba5 user: js | |
|
2022-11-27
| ||
| 17:45 | • New ticket [316edadc24]. artifact: 74018adb03 user: js | |
| Ticket UUID: | 316edadc2411d1b5e5597c32da432c72056ca771 | |||
| Title: | Add a cache in OFDNSResolver | |||
| Status: | Fixed | Type: | Feature_Request | |
| Severity: | Important | Priority: | Medium | |
| Subsystem: | Resolution: | Fixed | ||
| Last Modified: | 2024-01-14 13:33:42 | |||
| Version Found In: | Milestone: | 1.1 | ||
| User Comments: | ||||
|
js added on 2022-11-27 17:45:29:
Currently, js added on 2022-11-28 22:15:17: Actually, it probably makes more sense to add the cache in This cache probably makes most sense to be per-instance, even though that means there is no reuse between threads. But the added locking on every lookup is probably worse than just doing one lookup per thread. js added on 2023-07-15 14:39:00: This is not causing any problems and purely a performance optimization, so really shouldn't block 1.0. js added on 2023-12-29 16:30:06: Implemented by [252f11c431578d91] and [219aa9cf659c2a6d]. | ||||