etime granularity in access logs
Unlike DS, DPS 6.3 etimes in the access log are in millisecs.
For sake of performance, DPS uses a timeThread that gets the time
regularly (every 500ms only in DPS 6.3) instead of performing a system call each time the
current time is needed so etimes shown in access logs may be biased to a large extend and show 0ms when the effective etime is < 500ms. Conversaly , etimes may show a value of 500ms when the effective time is smaller.
TimeThread -----T1-----T2-----T3-----T4----T5 with (Ti- T()i-1)) = 500ms
DPS time retrieval example 1 | | => real value = 5ms, computed
value is T2-T2 = 0
DPS time retrieval example 2 | | => real value = 15ms,
computed value is T3-T2 = 500ms
The time "granularity" can be changed to accommodate with your needs in DPS 7.0 (available soon) but you can get a fix earlier (RFE 6601029) by contacting the Sun support team.
