-
Welcome
-
Subscribe to
Sponsors
PLATINUM SPONSORS
GOLD SPONSORS
SILVER SPONSORS
BRONZE SPONSORS
MEDIA SPONSORS
Maximizing VM writeout performance
*One Line Summary
Teach the VM subsystem to perform large I/O writeouts to avoid performance degradation in some situations.
Abstract
An application making explicit writeout requests for relatively large, contiguous blocks of I/O can produce good I/O patterns and achieve high throughput. However, when the VM goes into writeback, pages are written based on age and the kernel may not produces as optimal of an I/O pattern as the application had. As a result, application performance drops as the app-initiated writeout is slowed by tiny, discontiguous VM writeouts. An application that had been avoiding VM writeout by monitoring global memory levels will appear to regress when it is moved to a NUMA system where per-node or per-zone limits initiate VM writeback before global limits are reached.
I would like to discuss mechanisms to improve writeout performance. Ideas include teaching the VM writeback paths in the kernel to perform I/O is larger swathes, or grouping pages which should be written together in some fashion.
Speaker
-
Robert Jennings
IBM- Favorites: View Robert's favorites
Biography
Rob is a Linux kernel developer in IBM’s Linux Technology Center based in Austin, TX. He has been working on operating systems for over 12 years and the Linux kernel for 9 years in the areas of networking, SCSI, memory hot-plug, hibernation, live-migration, and powerpc virtualization.
Sessions
-
- Title: vmsplice with transparent huge pages
- Microconference: Scaling
- Time: 4:10pm
-
One Line Summary:
vmsplice() could move (rather can copy) pages between processes, but performance would be greatly improved if this supported THP.
- Speakers: Robert Jennings
