# Compilation performance

**URL:** <https://forums.swift.org/t/compilation-performance/4429>\
**Category:** Compiler\
**Created:** [November 3, 2016, 1:43am UTC](https://forums.swift.org/t/compilation-performance/4429 "2016-11-03T01:43:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Graydon\_Hoare](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/graydon_hoare/32/489_2.png) [@Graydon\_Hoare](https://forums.swift.org/u/Graydon_Hoare)\
**Post date:** [November 3, 2016, 1:43am UTC](https://forums.swift.org/t/compilation-performance/4429/1 "2016-11-03T01:43:36Z")

</div>

Hi,

I've been working a bit on testing infrastructure for systematically improving swiftc compilation performance. Attached is a document summarizing both the machinery I put together, and an example (small) bug recently fixed, as a case study showing how to use it.

I'd like to encourage folks interested in swiftc compile times to take a read through; especially if you happen to have an existing bug, or pattern of bad performance you're seeing (or even have a hunch about), I'd be interested to know if a scaling test can capture it. I'll be working through some compilation performance bugs using this framework for the next while, so if anyone would like to collaborate on investigating something, let me know and I'd be happy to help.

Thanks,

-Graydon

[CompilationPerformance.md](https://forums.swift.org/uploads/short-url/qEKU6CPaCgNnrka5LICp3EHQBEs.enc) (9.68 KB)

---

<div class="post-metadata">

**Author:** ![Ben\_Asher](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ben_asher/32/2753_2.png) [@Ben\_Asher](https://forums.swift.org/u/Ben_Asher)\
**Post date:** [November 4, 2016, 11:02pm UTC](https://forums.swift.org/t/compilation-performance/4429/2 "2016-11-04T23:02:08Z")

</div>

This is awesome. Thanks Graydon!!

Ben

> **···**
>
> On Wed, Nov 2, 2016 at 6:43 PM, Graydon Hoare via swift-dev \< swift-dev@swift.org\> wrote:
> 
> > Hi,
> > 
> > I've been working a bit on testing infrastructure for systematically  
> > improving swiftc compilation performance. Attached is a document  
> > summarizing both the machinery I put together, and an example (small) bug  
> > recently fixed, as a case study showing how to use it.
> > 
> > I'd like to encourage folks interested in swiftc compile times to take a  
> > read through; especially if you happen to have an existing bug, or pattern  
> > of bad performance you're seeing (or even have a hunch about), I'd be  
> > interested to know if a scaling test can capture it. I'll be working  
> > through some compilation performance bugs using this framework for the next  
> > while, so if anyone would like to collaborate on investigating something,  
> > let me know and I'd be happy to help.
> > 
> > Thanks,
> > 
> > -Graydon
> > 
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > swift-dev mailing list  
> > swift-dev@swift.org  
> > [https://lists.swift.org/mailman/listinfo/swift-dev](https://lists.swift.org/mailman/listinfo/swift-dev)
> 
> --  
> -Ben
