BEGIN:VCALENDAR
VERSION:2.0
PRODID:icalendar-ruby
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20260605T022312Z
UID:b8333931-0e26-48fc-92d0-152fdcc340cf
DTSTART;TZID=Canada/Pacific:20260603T133000
DTEND;TZID=Canada/Pacific:20260603T163000
DESCRIPTION:<html><ul><li>This event was exported from <a href="https://exp
 lora.alliancecan.ca/" target="_blank" rel="noopener"><strong>Explora</stro
 ng></a></li><li>The content provider for this event is: <a href="https://e
 xplora.alliancecan.ca/content_providers/west" target="_blank" rel="noopene
 r">SFU Research Computing Group</a></li><li><strong>Registration may be re
 quired for the event</strong>\, please visit the following URL to learn mo
 re: <a href="https://sfu26.netlify.app" target="_blank" rel="noopener">htt
 ps://sfu26.netlify.app</a></li></ul><hr><p><a href="https://sfu26.netlify.
 app" target="_blank" rel="noopener">Register</a><br><br>Abstract: R is no
 t a fast language. Poorly written R is <em>really slow! </em>Faced with s
 low code\, people tend to think “parallel” or “GPU” (which is an a
 djacent topic since GPUs allow to run many simple calculations in parallel
 ). Parallel programming can indeed greatly help speed up some types of cod
 e. A lot of hardware however is not the answer to poorly written code. Bef
 ore considering parallelization\, you should think of ways to optimize you
 r code sequentially because not all programs can be parallelized\, paralle
 l programming has costs and overheads\, and an optimized serial code will 
 also benefit your parallel code. In many cases\, writing better code will 
 save you more computing time than parallelization. This course will cover 
 just that: how to benchmark code\, how to identify bottlenecks\, and how t
 o greatly improve code performance without using additional hardware.</p><
 /html>
LOCATION:onsite
SUMMARY:R optimizations [summer school]
URL;VALUE=URI:https://sfu26.netlify.app
END:VEVENT
END:VCALENDAR
