Speaker
Description
It's no secret that to optimize R code one has to write it in C (or C++). This is, however, just a beginning. When does it make sense to rewrite the code? What are the typical performance sinkholes? What are the key techniques to get even more performance?
There are surprisingly few resources where you could find the answers, and my talk will try to fill that gap. Lately, I've been working on improving performance of {purrr} functions and at least one of these improvements already made it to the official release, speeding up every() and friends twice. I've learnt a lot and I want others to learn too, as there are too many packages to optimize for me to go at it alone.
If you used AI tools or services to support the preparation of this submission, please state the name and reason for using each of them.
No AI tools/services were used.
| Keywords: Please list up to 5 keywords to help us find the right session for your contribution. | C, performance |
|---|---|
| Virtual Option | This submission is for onsite presentation primarily, but I would also like it to be considered for pre-recorded virtual presentation if I don't get an onsite slot |
| Video Recording | Please don't share recordings of my talk |
| The author(s) agree(s) to take responsibility and be accountable for the contents of the submission and is/are authorized to present it. | Confirm |