Timezone isn't accessible, please provide the correct parameters
eventFeedUrl=http://realintelligence.com/customers/expos/00Do0000000aAt2/FMS_xmlcreator/a0J1J00001H0ji2_specific-event-list.xml
trackCategory=Session
eventID=a0J1J00001H0ji2
timezone=
duration=PTH
, NaNth
3:20-5:45 PM
PMEM-202-1: Persistent Memory Part 4: Current Research in Persistent Memory (Persistent Memory Track)
Paper Title: Exploiting Managed Language Semantics to Mitigate Wear-Out in Persistent Memory

Paper Abstract: Emerging persistent memories such as Phase Change Memory (PCM) offer more capacity than DRAM. Unfortunately, PCM suffers from high latency and limited write endurance. Emerging memory systems combine DRAM and PCM to form hybrid memories. Hardware wear-leveling then spreads writes out across the entire PCM capacity. Even with wear-leveling, popular Java applications running on top of a PCM-only system leads to impractical PCM lifetimes. Also, coarse-grained OS approaches that migrate highly-written pages to DRAM bear several inefficiencies. In this talk, I will motivate garbage collection in managed runtimes such as the Java Virtual Machine as an abstraction to mitigate PCM wear-out in hybrid DRAM-PCM memories. I will show a detailed analysis of writes in popular Java applications: (1) distribution of writes over objects in the virtual heap, and (2) distribution of writes by allocation-site in Java programs. The key insights from this analysis lead to a new class of write-rationing garbage collectors that exploit fine-grained object behaviors in Java applications to limit PCM writes. They extend PCM lifetime by placing highly written objects in DRAM and the rest in PCM. I will discuss Kingsguard, a write-rationing garbage collector that dynamically monitors writes to place highly written objects in DRAM. I will then introduce Crystal Gazer, a profile-driven write-rationing garbage collector that exploits static profiling of writes on a per allocation-site basis to place highly written objects in DRAM. Write-rationing garbage collection makes PCM a practical DRAM replacement by aggressively limiting writes to it in a hybrid memory configuration. It requires no extra hardware and OS support and enables the use of PCM for commodity applications by leaving the programming language and model unchanged.

Paper Author: Shoaib Akram, Assistant Professor, Australian National University

Author Bio: I am a Ph.D. student in the Department of Electronics and Information Systems at Ghent University in Belgium. I am pursuing my degree under the supervision of Lieven Eeckhout. Before moving to Ghent in 2012, I spent two years as an Early Stage Researcher at the Foundation of Research and Technology (FORTH) in Heraklion, Greece. My research at FORTH was funded by an EU Marie Curie fellowship. I got my M.S. in Electrical and Computer Engineering at the University of Illinois at Urbana Champaign in 2009. I was a recipient of the J. William Fulbright scholarship from the U.S. Department of State. Before all the foreign travels, I got my B.Sc. in Electrical Engineering in 2006 from the University of Engineering and Technology in Lahore, Pakistan.