On Mon, 3 Jun 2024 06:13:35 GMT, lingjun-cg wrote:
>> ### Performance regression of DecimalFormat.format
>> From the output of perf, we can see the hottest regions contain atomic
>> instructions. But when run with JDK 11, there is no such problem. The
>> reason is the removed biased locking.
On Mon, 3 Jun 2024 06:13:35 GMT, lingjun-cg wrote:
>> ### Performance regression of DecimalFormat.format
>> From the output of perf, we can see the hottest regions contain atomic
>> instructions. But when run with JDK 11, there is no such problem. The
>> reason is the removed biased locking.
> ### Performance regression of DecimalFormat.format
> From the output of perf, we can see the hottest regions contain atomic
> instructions. But when run with JDK 11, there is no such problem. The reason
> is the removed biased locking.
> The DecimalFormat uses StringBuffer everywhere, and St
### Performance regression of DecimalFormat.format
>From the output of perf, we can see the hottest regions contain atomic
>instructions. But when run with JDK 11, there is no such problem. The reason
>is the removed biased locking.
The DecimalFormat uses StringBuffer everywhere, and StringBuf
