[swift-users] Improving compilation times?

piotr gorzelany piotr.gorzelany at gmail.com
Wed Mar 22 15:03:41 CDT 2017

Hi, I hope I reached the right mailing list to ask a question about tooling.

Can somebody from the compiler or Xcode team share some tips on how to
improve compilation times of larger Swift projects?

I am an iOS developer and the largest issue my team has with Swift so far
is that when the project gets semi large (~30 000 lines) the compilation
times start to be high (~10 minutes from clean). This is a MAJOR downside
since iOS development oftentimes requires rapid changes to UI or logic.
Every person of my team compiles a project at least 10 times a day to test
new features or functionalities. When compilation times start to be higher
than 10 minutes that gets us to ~1.5h a day of developer time spend just on
compiling. Not to mention the focus lost when this is happening.

I know the Swift Evolution list is buzzing with new ideas and features but
from my experience the compilation times is a CRITICAL thing to improve in
the next Swift release since it cost real money to waste all those
developer hours. Just think of all the hours lost on compiling across all
Swift devs worldwide and you will get to probably dozens of thousand of dev
hours a day.

Is the core compiler team going to address compilation performance in the
next release?

Maybe there is an existing solution to long compilation times that we don't
know of? It would be great if anybody could share.
I was thinking maybe of dividing the app into multiple frameworks since I
think frameworks are compiled only once only on change?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20170322/6acdb800/attachment.html>

More information about the swift-users mailing list