netty5

History

Norman Maurer 2278991db7 Use addAndGet(...) as a replacement for compareAndSet(...) when tracking the direct memory usage. (#8596 ) Motivation: We can change from using compareAndSet to addAndGet, which emits a different CPU instruction on x86 (CMPXCHG to XADD) when count direct memory usage. This instruction is cheaper in general and so produce less overhead on the "happy path". If we detect too much memory usage we just rollback the change before throwing the Error. Modifications: Replace compareAndSet(...) with addAndGet(...) Result: Less overhead when tracking direct memory.	2018-11-27 08:33:28 +01:00
..
main	Use addAndGet(...) as a replacement for compareAndSet(...) when tracking the direct memory usage. (#8596 )	2018-11-27 08:33:28 +01:00
test	Log the correct line-number when using SLF4j with netty if possible. (#8258 )	2018-09-07 07:34:22 +02:00

Use addAndGet(...) as a replacement for compareAndSet(...) when tracking the direct memory usage. (#8596 )

Motivation:

We can change from using compareAndSet to addAndGet, which emits a different CPU instruction on x86 (CMPXCHG to XADD) when count direct memory usage. This instruction is cheaper in general and so produce less overhead on the "happy path". If we detect too much memory usage we just rollback the change before throwing the Error.

Modifications:

Replace compareAndSet(...) with addAndGet(...)

Result:

Less overhead when tracking direct memory.

2018-11-27 08:33:28 +01:00

main

Use addAndGet(...) as a replacement for compareAndSet(...) when tracking the direct memory usage. (#8596 )

2018-11-27 08:33:28 +01:00

test

Log the correct line-number when using SLF4j with netty if possible. (#8258 )

2018-09-07 07:34:22 +02:00