FLASH MEMORY FOR FULL-THROTTLE GPU ACCELERATION

Transcription

1 FLASH MEMORY FOR FULL-THROTTLE GPU ACCELERATION

2 Vincent Brisebois 12 years at Autodesk Media & Entertainment Tech Support / Product Specialist / Product Designer Member of the Visual Effects Society Technology Council 2 years at Fusion-io Entertainment Business Development Performance Computing Industry Manager

3 Relative Performance THE DATA SUPPLY PROBLEM LEADS TO IDLE CAPACITY Growing Performance Gap CPUs Memory Storage According to Moore's Law, processing performance doubles every 18 months 3

4 FOUNDER & CEO DAVID FLYNN

5 TECHNOLOGY ENABLERS FLASH MEMORY PCIe ECOSYSTEM SOFTWARE-ENABLED REPROGRAMMABLE CONTROLLERS

6 ARCHITECTURAL HIGHLIGHTS NAND Flash Chips Reliability Heat Sink/FPGA Parity Chip N+1 redundancy Like having a RAID between chips Without the capacity sacrifice Over Provisioning Reserve space for handling individual pixels dying Reserve space is adjustable if higher write performance is needed High ECC strength 72 bit error correction

7 NETWORKED STORAGE DATA SUPPLY CHAIN FROM APPLICATION TO FLASH Application Server Processor Network Adapter Network Switch Network Adapter Storage Appliance Processor Disk RAID Controller SAS/SATA Bus and Protocol SSD Embedded CPU SSD Battery/Sup RAM er Capacitors NAND Flash 9 Intermediary components required All adding access delay, cost, complexity, and lowering reliability (especially the super capacitors) Requests must do a round trip touching everything TWICE May 24, 2012 Fusion-io Confidential 7

8 SSD DATA SUPPLY CHAIN FROM APPLICATION TO FLASH Application Server Processor Disk RAID Controller SAS/SATA Bus and Protocol SSD Embedded CPU SSD Battery/Sup RAM er Capacitors NAND Flash 5 Intermediary components required All adding access delay, cost, complexity, and lowering reliability (especially the super capacitors) May 24, 2012 Fusion-io Confidential 8

9 FUSION-IO DATA SUPPLY CHAIN FROM APPLICATION TO FLASH Application Server Processor NAND Flash 0 Intermediary components required No need for super capacitors because data is not "buffered in DRAM May 24, 2012 Fusion-io Confidential 9

10 FUSION-IO FIRST MOVER MILESTONES Mission to consolidate memory and storage iomemory technology unveiled First products launched 1 million IOPS IBM Quicksilver Dell strategic investment HP OEMs products IBM OEMs products Samsung strategic investment Dell OEMs products introduced IPO on NYSE ioturbine acquired iodrive2 announced 50+ Petabytes shipped 1 Billion IOPS 2,500 customers >120 channel and alliance partners iofx iomemory SDK May 24,

11 CHIEF SCIENTIST STEVE WOZNIAK

12 PERFORMANCE COUNTS 12

13 COMPREHENSIVE CUSTOMER SUCCESS F I N A N C I A L S W E B T E C H N O L O G Y R E T A I L M A N U F A C T U R I N G / G O V E R N M E N T The world s leading Q&A site FASTER DATA 5x ANAL YSIS FASTER DATAB ASE 30x REPLICATION FASTER DATA W AREHOUSE 40x QUERIES QUERY PROCESSING 15x THROUGHPUT FASTER 15x QUERIES 30+ case studies at May 24,

14 FUSION-IO ACCELERATES Databases Virtualization Search Analytics Big Data Collaboration INFORMIX KVM ORACLE Text Lotus HPC Messaging Workstation Development Caching Security/Logging Web MQ LAMP GPFS May 24,

15 IOMEMORY PLATFORM May 24,

16 FUSION IOFX MEMORY TIER Tuned for sustained performance in multithreaded applications Work on 2K, 4K and 5K digital content interactively, in full resolution Manipulate stereoscopic content in real-time Accelerate video and image editing and compositing Speed video playback Powerful throughput to maximize GPU processing Simplify and accelerate encoding and transcoding Accelerate compiling code for software programmers 420GB 1.4 GB/s Read 700MB/s Write 42µs QDP MLC May 24,

17 IOMEMORY PERFORMANCE Capacity 365GB Duo 2.4TB 400GB Duo 1.2TB iofx NAND Type MLC MLC SLC SLC MLC Read Bandwidth 910 MB/s 3.0 GB/s 1.4 GB/s 3.0 GB/s 1.5 GB/s Write Bandwidth 590 MB/s 2.5 GB/s 1.3 GB/s 2.6 GB/s 700 MB/s Read IOPS (Seq) 415, , , ,000 Write IOPS (Seq) 535, , , ,000 Read IOPS (Rand) 137, ,000 Write IOPS (Rand) 535, ,000 Read Latency 68 us 68 us 47 us 47 us 68 us Write Latency 15 us 15 us 15 us 15 us 15 us Bus Interface PCIe 2.0 x4 PCIe 2.0 x8 PCIe 2.0 x4 PCIe 2.0 x8 PCIe 2.0 x4 May 24,

18 Remote Host Host Application Application FLASH MEMORY EVOLUTION Native Access Legacy SSDs iomemory as Block Device iomemory as Transparent Cache iomemory with direct access I/O iomemory with memory semantics Application Application Application Application Application Open Source Extensions Open Source Extensions OS Block I/O OS Block I/O OS Block I/O Direct-access I/O API Family Memory Semantics API Family File System File System File System Block Layer SAS/SATA Network RAID Controller Flash Layer Block Layer Virtual Storage Layer Block Layer directcache directfs native file system service directfs Read/Write Read/Write Read/Write Read/Write Read/Write Load/Store May 24,

19 Remote Host Host Application Application FLASH MEMORY EVOLUTION Native Access Legacy SSDs iomemory as Block Device iomemory as Transparent Cache iomemory with direct access I/O iomemory with memory semantics Application Application Application Application Application Direct I/O Open Source Extensions Open Source Extensions OS Block I/O OS Block I/O OS Block I/O Direct-access I/O API Family Memory Semantics API Family File System File System File System Block Layer SAS/SATA Network RAID Controller Flash Layer Block Layer Virtual Storage Layer Block Layer directcache directfs native file system service directfs Read/Write Read/Write Read/Write Read/Write Read/Write Load/Store May 24,

20 IOMEMORY AS BLOCK DEVICE Demo May 24,

21 SYSTEM DIAGRAM May 24,

22 QUADRO DUAL COPY ENGINE May 24,

23 OPENGL PIXEL BUFFER OBJECTS (PBO) File system direct I/O file_handle = CreateFile(LPCSTR(video_file), GENERIC_READ, FILE_SHARE_READ, NULL, OPEN_EXISTING, FILE_FLAG_NO_BUFFERING, NULL); GPU DMA-able system buffer glgenbuffers(1, &buffer_handle); glbindbuffer(gl_pixel_unpack_buffer_arb, buffer_handle); glbufferdata(gl_pixel_unpack_buffer_arb, size, NULL, GL_DYNAMIC_DRAW); glbindbuffer(gl_pixel_unpack_buffer_arb,0); May 24,

24 READ FROM IOMEMORY Map PBO for write glbindbuffer(gl_pixel_pack_buffer_arb, buffer_handle); void pbomem = glmapbuffer(gl_pixel_pack_buffer_arb, GL_WRITE_ONLY); glbindbuffer(gl_pixel_pack_buffer_arb,0); Read from iomemory BOOL ret = ReadFile(file_handle, pbomem, size, &num_bytes_read, NULL); Unmap PBO for DMA glbindbuffer(gl_pixel_pack_buffer_arb, buffer_handle); glunmapbuffer(gl_pixel_pack_buffer_arb); glbindbuffer(gl_pixel_pack_buffer_arb,0); May 24,

25 TRANSFER TO GPU glbindbuffer(gl_pixel_unpack_buffer_arb, buffer_handle); glbindtexture(gl_texture_2d, texture_handle); glteximage2d(gl_texture_2d, 0, GL_RGBA8, width, height, 0, GL_BGRA, GL_UNSIGNED_BYTE, 0); glbindtexture(gl_texture_2d, 0); glbindbuffer(gl_pixel_unpack_buffer_arb, 0); Barrier sync DMA GLsync fence = glfencesync(gl_sync_gpu_commands_complete, 0); glclientwaitsync(fence,0,0); gldeletesync(fence); May 24,

26 PIPELINE Read from iomemory DMA to GPU Draw from GPU iofx iofx May 24,

27 CUDA GPU DIRECT Copy data directly to/from CUDA pinned host memory Avoid one copy Peer to peer transfers between GPUs Utilizes PCIe DMA Peer to peer memory access between GPUs NUMA from within CUDA kernels Pipeline transfers for GP-GPU Read from iomemory Write to iomemory Unified Virtual Address Space! May 24,

28 CUDA OS-pinned CUDA buffer // Alloc OS-pinned memory cudahostalloc((void**)&h_odata, memsize, (wc)? cudahostallocwritecombined : 0); Read from iomemory fd = open("/mnt/cudamemory", O_RDWR O_DIRECT); if (fd!= 0) { rc= read(fd, h_odata, memsize); Copy (DMA) to GPU cudamemcpyasync(d_idata, h_odata, memsize, cudamemcpyhosttodevice, stream); May 24,

29 PROGRAMMING PATTERNS Pipelines CPU threads CUDA streams Ring buffers Parallel DMA Direct I/O But iomemory is much more than a block device It s non-volatile memory with native access semantics May 24,

30 EXPLOITING NATIVE CHARACTERISTICS OF IOMEMORY 1. Native log-append writes incorporates copy-on-write basics 2. Native block mapping and allocation incorporate file system basics 3. Native large virtual address space incorporates sparse semantics 4. Native storage methods incorporate key-value store basics May 24,

31 SDK INTRO Fusion-io Software Development Kit Enables Native Flash Memory Access: directprimitives API, including Atomic Writes and the MySQL InnoDB extension directkey-value Store API * directfs, native file-access layer * Auto-Commit Memory API Extended Memory API May 24,

32 Remote Host Host direct I/O Primitives direct Key-Value Store API direct Cache API Application Application FLASH MEMORY EVOLUTION: NATIVE API ACCESS Native Access Legacy SSDs iomemory as Block Device iomemory as Transparent Cache iomemory with direct access I/O Application Application Application Application Open Source Extensions OS Block I/O OS Block I/O OS Block I/O File System File System File System Block Layer SAS/SATA Network RAID Controller Flash Layer Block Layer Virtual Storage Layer Block Layer directcache Read/Write Read/Write Read/Write Read/Write directfs native file system service May 24,

33 Remote Host Host direct I/O Primitives direct Key-Value Store API direct Cache API Application Application FLASH MEMORY EVOLUTION: NATIVE API ACCESS Native Access Legacy SSDs iomemory as Block Device iomemory as Transparent Cache iomemory with direct access I/O Application Application Application Application Open Source Direct I/O Extensions OS Block I/O OS Block I/O OS Block I/O File System File System File System Block Layer SAS/SATA Network RAID Controller Flash Layer Block Layer Virtual Storage Layer Block Layer directcache Read/Write Read/Write Read/Write Read/Write directfs native file system service May 24,

34 KEY-VALUE STORE API LIBRARY Application Key Value API and Library atomic write() Lookup: exists() Atomic delete (PTRIM) Coordinated Garbage Collection Dynamic provisioning, Block allocation, logging etc. Citrusleaf NoSQL Demo April ,000 transactions/second on a single server May 24,

35 CUDA & KEY-VALUE STORE OS-pinned CUDA buffer // Alloc OS-pinned memory cudahostalloc((void**)&h_odata, memsize, (wc)? cudahostallocwritecombined : 0); KeyGet from iomemory rc = directkeyget( key, h_odata, &memsize); Copy (DMA) to GPU cudamemcpyasync(d_idata, h_odata, memsize, cudamemcpyhosttodevice, stream); May 24,

36 DIRECTFS NATIVE FILE SERVICES LAYER Application DirectFS Namespace File/Offset ->Sparse Address atomic write() Lookup: exists() Atomic delete (PTRIM) Dynamic provisioning, Block allocation, logging etc. May 24,

37 CUDA & DIRECTFS OS-pinned CUDA buffer // Alloc OS-pinned memory cudahostalloc((void**)&h_odata, memsize, (wc)? cudahostallocwritecombined : 0); Read from iomemory fd = open("/mnt/cudamemory", O_RDWR O_DIRECT); if (fd!= 0) { rc= read(fd, h_odata, memsize); Copy (DMA) to GPU cudamemcpyasync(d_idata, h_odata, memsize, cudamemcpyhosttodevice, stream); May 24,

38 Remote Host Host direct I/O Primitives direct Key-Value Store API direct Cache API Extended Memory Checkpointed Memory Auto-Commit Memory Application Application FLASH MEMORY EVOLUTION: NATIVE API ACCESS Native Access Legacy SSDs iomemory as Block Device iomemory as Transparent Cache iomemory with direct access I/O iomemory with memory semantics Application Application Application Application Application Open Source Extensions Open Source Extensions OS Block I/O OS Block I/O OS Block I/O File System File System File System Block Layer SAS/SATA Network RAID Controller Flash Layer Block Layer Virtual Storage Layer Block Layer directcache directfs native file system service directfs Read/Write Read/Write Read/Write Read/Write Read/Write Load/Store May 24,

39 CONCLUSION Early-access to iomemory SDK libraries and technical documentation iomemory SDK Web Seminars: Wednesday May 2 May 9 May 23 May 30 June 6 directprimitives API, including Atomic Writes and the MySQL InnoDB extension directkey-value Store API directfs, native file-access layer Auto-Commit Memory API Extended Memory API May 24,

40 WHAT WE WANT TO SEE We encourage you to Go Native and engage us in discussion as to where you want to see the technology grow. We would love your input. May 24,

41 T H A N K Y O U