Call for Talks Opens
Wednesday, August 16, 2017
Call for Talks Closes at 11:59 PM (Pacific)
Friday, October 20, 2017
Final Notifications Sent By
Friday, Dec. 8, 2017
Submit your work by October 20, 2017.
Submissions must be about your work using GPUs. It can be completed work or work currently in progress. Submissions must provide actual or expected results/accomplishments and must demonstrate a significant innovation or improvement using GPU computing.
Talk Review Process
The GTC Content Committee will review, rate, and select submissions based on:
Technical details and performance results offered and insights to be learned
Relevance and timeliness of the presentation to GPU computing
Presenter credentials and expertise in the subject matter
Presenter public speaking experience(s)
If your submission is focused on a service, technology, or a new product your company is offering, please contact us for information on sponsored session opportunities.
You will be required to provide the following information in your submission:
Submitter's Contact Information: Email and phone number
Session Title: Maximum of 12 words. Should be enticing and concisely tell attendees what your session is about.
Session Format & Duration: 25-minute Talk (maximum 1 presenter); 50-minute Talk (maximum 2 presenters); 50-minute Panel (maximum 5 presenters); 80-minute Tutorial (maximum 3 presenters); 80-minute Hands-on Labs (maximum 3 presenters)
Audience Level: Beginner; Intermediate; Advanced. Beginner: Limited or no prior knowledge or experience is required. Session helps attendees learn the fundamentals of a subject area. Intermediate: Some knowledge of the subject area is required. Session helps attendees enhance their knowledge of a subject area. Advanced: Greatly developed knowledge of the subject area is required. Session helps attendees heighten their already advanced knowledge of a subject area.
Topics: Select up to three topics from a dropdown list of pre-approved topic areas.
Session Description: Maximum 800 characters (approximately 150 words) – for use on an online scheduler, mobile app and other online marketing tools. The Session Description must explain what the attendee will learn from your presentation.
Extended Abstract & Results: Maximum 3000 characters (approximately 500 words) – provide details on what your session is about including examples and actual or expected results/accomplishments that will help the Content Committee better understand the technical merits of your submission. The Extended Abstract will not be published.
Presenter's Information: Email and cell phone number (can be different from submitter's information; only used for emergency purposes at live event if submission is accepted)
Presenter Biography: Maximum 100 words
Presenter Headshot: No less than 1800x2700px and no more than 2400x3000px. Maximum file size: 32 MB.
Presenter Agreement: To be considered for a session the Presenter Agreement must be completed
Permission to Webcast and/or Record: A confirmation of whether or not you agree to be recorded and/or webcast is needed.
Supporting Material: is required to assist the Content Review Committee in better understanding your work. Provide supplemental information that supports your session proposal. Additional materials may include white papers, research work, videos, images, demos, proof of concept, etc.
EXAMPLE OF STELLAR SUBMISSION
How to Write a Great Session Title
Your session title is what gets the reader to read the first sentence of the session description. Clearly articulated session titles that have clear learning objectives along with a dash of pizzazz greatly increase the chance that conference attendees will attend the session.
The title should:
Be USEFUL to the reader
Provide the reader with a sense of URGENCY
Convey the idea that there is a UNIQUE benefit to attending
How to Write a Great Session Description
The first sentence should describe what the attendee can expect to learn from your presentation (e.g. "Learn about extensions that enable efficient use of PGAS models.") Avoid background your audience already knows (e.g., "Originally designed as graphics accelerators, GPUs have evolved into powerful parallel processors capable of accelerating many compute-intensive applications."). Subsequent sentences should offer more details about what will be covered and why the reader should attend. In general, go for clarity over cleverness.
The description should begin with an action word such as:
Learn how to…
Explore new techniques in…
Hear product experts explain how…
See the newest features in…
Dive deep into the…
Join industry experts for a discussion on…
Get the latest information on…
Select the correct duration for your submission:
GTC is soliciting submissions that provide concrete examples and contain both practical and theoretical information.
A 25-minute Talk provides attendees with concise, focused content on a specific topic or specific aspect of a broader topic.
A 50-minute Talk provides attendees with an expansive discussion of a topic. It covers two or more areas of a broad technical topic or provides a detailed overview or case study of the topic.
A 50-minute Panel is an interactive grouping of experts discussing a topic that is best covered from multiple viewpoints.
An 80-minute Tutorial provides attendees with in-depth coverage of a technical topic.
We require one speaker for a 25-minute talk; two speakers may be accepted for a 50-minute talk if you can demonstrate the second person is necessary by describing their role in the presentation. 50-minute panels should have no more than five speakers and an 80-minute tutorial no more than three speakers.
Examples of GTC submission descriptions:
Session Title: Faster, Cheaper, Better – Hybridization of Linear Algebra for GPUs
Session Description: Learn how to develop faster, cheaper and better linear algebra software for GPUs through a hybridization methodology that is built on (1) Representing linear algebra algorithms as directed acyclic graphs where nodes correspond to tasks and edges to dependencies among them, and (2) Scheduling the execution of the tasks over hybrid architectures of GPUs and multicore. Examples will be given using MAGMA, a new generation of linear algebra libraries that extends the sequential LAPACK-style algorithms to the highly parallel GPU and multicore heterogeneous architectures.
Session Title: Analysis-Driven Performance Optimization: A New Approach to Determining Performance Thresholds
Session Description: The goal of this session is to demystify performance optimization by transforming it into an analysis-driven process. There are three fundamental limiters to kernel performance: instruction throughput, memory throughput, and latency. In this session we will describe: how to use profiling tools and source code instrumentation to assess the significance of each limiter; what optimizations to apply for each limiter; how to determine when hardware limits are reached. Concepts will be illustrated with some examples and are equally applicable to both CUDA and OpenCL development. It is assumed that registrants are already familiar with the fundamental optimization techniques.
Extended Abstract Example
Our runtime designs focus on performance while ensuring truly one-sided progress of communication which is critical for PGAS models. These designs demonstrate significant potential for the users of PGAS models as well as hybrid MPI+PGAS models (as available in MVAPICH2-X) to take advantage of NVIDIA GPUs. The extensions in OpenSHMEM, coupled with an optimized runtime, improve the latency of GPU-GPU shmem-getmem operation by up to 90%, 45% and 42%, for intra-IOH (I/O Hub), inter-IOH and inter-node configurations. The proposed extensions and the associated runtime reduces the latency of 4 bytes Put to 2.7us from GPU-to-GPU. The proposed enhancements improve the performance of Stencil2D kernel by 65% on a cluster of 192 GPUs and the performance of BFS kernel by 12% on a cluster of 96 GPUs. As part of the talk, we will use benchmarks from the popular OSU micro-benchmark suite and application kernels to demonstrate how to use the new extensions and extract performance benefits from the associated runtime designs.