[ https://issues.jboss.org/browse/JGRP-1871?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1871: -------------------------------- If it's only {{up_prot}} and {{down_prot}}, then that's fine as they're mostly read and only written at stack init time, so that's fast. However, making other fields {{volatile}} can have a big impact on perf: the memory barriers established by volatile fields potentially trigger a lot of cache line flushes and (especially with false sharing) a lot of reloading. No problem if this is mostly reads, but fields with a lot of writes might slow things down a lot. Even worse: testing this might yield good perf on one architecture, but bad perf on another; e.g. when cache line sizes differ. Since 1998 the stack architecture has been the same and no-one has ever run into this except WF... -- This message was sent by Atlassian JIRA (v6.2.6#6264)