Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
mechanical-sympathy
Conversations
Labels
CPU
CoordinatedOmission
DirectByteBuffer
Disruptor
G1
GC
GPU
Generics
HdrHistogram
Heap
Histogram
Hotspot
JNI
Java
JavaScript
Latency
LatencyStats
List
LockFree
MRI
Netty
Node
OpenJDK
Performance
PrintCompilation
ProgramOrder
ResponseTimeMeasurement
SBE
Safepoint
SequentialConsistency
TTSP
algorithms
alternative
api
arraycopy
asm
assembly
azul
basics
benchmarking
c
caliper
call
cassandra
chronicle
communication
comparison
concept
concurrency
correctness
design
development
doublehistogram
energy
engineering
exchange
feedback-requested
futex
gRPC
happens-before
historical
idea
innovation
interface
intrinsic
introduction
invention
jdk
jhiccup
jmh
jmm
jmx
jvm
kernel
koloboke
linux
logging
mechanical
memory
method
metrics
mq
off-heap
openHFT
os
power
presentation
process
project
queue
real-time
safepoint
scala
scalability
scalable
scylladb
sharding
shared
struct
syscall
system
task-pool
technology
threads
trading
trove
tutorial
unsafe
v8
varargs
zeromq
zipkin
About
mechanical-sympathy
Contact owners and managers
1–1 of 872
Welcome to the Mechanical Sympathy group. This group is for discussing how to code sympathetically for the underlying stack/platform so good performance can be extracted.
Mark all as read
Report group
0 selected
kedar mhaswade
,
Attila-Mihaly Balazs
2
10/10/13
Demonstrating surprising but correct behavior of sequentially consistent program ...
I think the code shows that currentTimeMillis is not synchronized across cores rather than timing
unread,
ProgramOrder
SequentialConsistency
correctness
Demonstrating surprising but correct behavior of sequentially consistent program ...
I think the code shows that currentTimeMillis is not synchronized across cores rather than timing
10/10/13