(S) RFR: 8154710: [Solaris] Investigate use of in-memory low-resolution timestamps for Java and internal time API's
david.holmes at oracle.com
Fri Apr 29 10:05:24 UTC 2016
On 29/04/2016 7:50 PM, Aleksey Shipilev wrote:
> On 04/29/2016 02:09 AM, David Holmes wrote:
>> bug: https://bugs.openjdk.java.net/browse/JDK-8154710
>> webrev: http://cr.openjdk.java.net/~dholmes/8154710/webrev/
> Looks good.
> Is hrtime_t always integral, so you can "(hrtime_t)now /
> NANOSECS_PER_MILLISEC" it?
Yes it is a 64-bit (long long) signed integer.
>> This change is small in nature but somewhat broad in scope. It "affects"
>> the implementation of System.currentTimeMillis() in the Java space, and
>> os::javaTimeMillis() in the VM. But on Solaris only.
>> I say "affects" but the change will be unobservable other than in terms
>> of performance.
> Observable enough to me.
:) Any apps you can think of that might show benefit from this?
More information about the core-libs-dev