[tickets] [opensaf:tickets] #1704 imm: Use nanosecond resolution for time measurements

2016-08-29 Thread Hung Nguyen 
- **status**: review --> fixed
- **Comment**:

default (5.1) [staging:6b6806]

changeset:   7986:6b6806ad5d27
user:Hung Nguyen 
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 opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1704 imm: Use nanosecond resolution for time measurements

2016-08-28 Thread Hung Nguyen 
- **status**: fixed --> review
- **Comment**:

Sent out a patch to fix the problem with IMMND resending intro messages 
constantly
https://sourceforge.net/p/opensaf/mailman/message/35308571/

~~~
Aug 28 09:36:38 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.101825
Aug 28 09:36:38 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.202881
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.303848
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.405328
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.506821
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.608214
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.709692
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.811176
Aug 28 09:36:39 SC-2 osafimmnd[439]: WA Resending introduce-me - problems with 
MDS ? 0.912262 
~~~




---

** [tickets:#1704] imm: Use nanosecond resolution for time measurements**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Fri Mar 18, 2016 10:08 AM UTC by Anders Widell
**Last Updated:** Wed Aug 24, 2016 09:42 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 opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1704 imm: Use nanosecond resolution for time measurements

2016-08-24 Thread Hung Nguyen 
- **status**: review --> fixed
- **Comment**:

default (5.1)

[staging:69f8a2]
changeset:   7953:69f8a21309ac
user:Hung Nguyen 
date:Thu Aug 04 14:37:14 2016 +0700
summary: imm: Use high resolution time measurements for ImmModel [#1704]

[staging:6248e8]
changeset:   7954:6248e8e83ad4
user:Hung Nguyen 
date:Thu Aug 04 15:39:09 2016 +0700
summary: imm: Use high resolution time measurements for IMMND server [#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:** Tue Aug 23, 2016 03:41 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 opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1704 imm: Use nanosecond resolution for time measurements

2016-08-22 Thread Hung Nguyen 
- **status**: accepted --> review



---

** [tickets:#1704] imm: Use nanosecond resolution for time measurements**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Fri Mar 18, 2016 10:08 AM UTC by Anders Widell
**Last Updated:** Tue Jul 26, 2016 08:11 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 opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1704 imm: Use nanosecond resolution for time measurements

2016-07-26 Thread Hung Nguyen 
- **status**: unassigned --> accepted
- **assigned_to**: Hung Nguyen
- **Part**: - --> nd
- **Milestone**: future --> 5.1.FC



---

** [tickets:#1704] imm: Use nanosecond resolution for time measurements**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Fri Mar 18, 2016 10:08 AM UTC by Anders Widell
**Last Updated:** Fri Mar 18, 2016 10:08 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 opensaf-tickets@lists.sourceforge.net 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.--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets