- **status**: review --> fixed
- **Comment**:
default (5.1) [staging:6b6806]
changeset: 7986:6b6806ad5d27
user: Hung Nguyen <[email protected]>
date: Sun Aug 28 09:28:34 2016 +0700
summary: imm: Avoid jobDurationSec of zero [#1704]
---
** [tickets:#1704] imm: Use nanosecond resolution for time measurements**
**Status:** fixed
**Milestone:** 5.1.FC
**Created:** Fri Mar 18, 2016 10:08 AM UTC by Anders Widell
**Last Updated:** Sun Aug 28, 2016 06:29 AM UTC
**Owner:** Hung Nguyen
There are currently time measurements for timeout handling in **ImmModel**, and
possibly other places in the IMM service, that use low resolution time
measurements. This is caused by using the **time_t** type for time stamps,
which only has a resolution of seconds. A consequence of this is that the
actual timeout can vary up to one second, depending on when (how long after the
last clock "tick") the timer is started.
Instead, nanosecond resolution should be used. The **osaf_clock_gettime()**
utility function declared in *osaftime.h* can be used to read the system clock
with nanosecond resolution. Another option in C++ is to use
**std::chrono::steady_clock**.
This ticket can be seen as a continuation of ticket [#1617], where we started
to use **osaf_clock_gettime()** but still didn't change the type of the
variables containing time-stamps from **time_t** to **struct timespec**.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
