201. Reality check: servers in 2014
Retail prices, major web server store (US $, circa 2014)
24 vCore, 128GB server ≈ $4K
32 vCore, 256GB server ≈ $8K
32 vCore, 384GB server ≈ $10K
64 vCore, 1TB server ≈ $24K
202. Reality check: servers in 2014
Retail prices, major web server store (US $, circa 2014)
24 vCore, 128GB server ≈ $4K
32 vCore, 256GB server ≈ $8K
32 vCore, 384GB server ≈ $10K
64 vCore, 1TB server ≈ $24K
Cheap (< $1/GB/Month), and roughly linear to ~1TB
203. Reality check: servers in 2014
Retail prices, major web server store (US $, circa 2014)
24 vCore, 128GB server ≈ $4K
32 vCore, 256GB server ≈ $8K
32 vCore, 384GB server ≈ $10K
64 vCore, 1TB server ≈ $24K
Cheap (< $1/GB/Month), and roughly linear to ~1TB
10s to 100s of GB/sec of memory bandwidth
231. What quality of GC is responsible
for the Application Memory Wall?
232. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
233. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
It is NOT about speed
Average speeds, 90%, 95% speeds, are all perfectly fine
234. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
It is NOT about speed
Average speeds, 90%, 95% speeds, are all perfectly fine
It is NOT about minor GC events (right now)
GC events in the 10s of msec are usually tolerable for most apps
235. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
It is NOT about speed
Average speeds, 90%, 95% speeds, are all perfectly fine
It is NOT about minor GC events (right now)
GC events in the 10s of msec are usually tolerable for most apps
It is NOT about the frequency of very large pauses
236. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
It is NOT about speed
Average speeds, 90%, 95% speeds, are all perfectly fine
It is NOT about minor GC events (right now)
GC events in the 10s of msec are usually tolerable for most apps
It is NOT about the frequency of very large pauses
It is ALL about the worst observable pause behavior
People avoid building/deploying visibly broken systems
237. What quality of GC is responsible
for the Application Memory Wall?
It is NOT about overhead or efficiency:
CPU utilization, bottlenecks, memory consumption and utilization
It is NOT about speed
Average speeds, 90%, 95% speeds, are all perfectly fine
It is NOT about minor GC events (right now)
GC events in the 10s of msec are usually tolerable for most apps
It is NOT about the frequency of very large pauses
It is ALL about the worst observable pause behavior
People avoid building/deploying visibly broken systems
284. Some
GC
tuning
flags
(although
some
are
absolute
now)
Source:
Word
Cloud
created
by
Frank
Pavageau
in
his
Devoxx
FR
2012
presentaGon
Gtled
“Death
by
Pauses”