I've been having an issue, which I know I've seen others mention online a while back when I was looking into how to decrease my compile times. Did some googling, learned about Assembly files, and implemented them. My compile times dropped from like 28 seconds to about 2.8 seconds. Woohoo! But - the longer Unity is open, the more updates I do, the compile times each time that I save/update a script and hit play increases. Yesterday I was at about 9 seconds. Now, after saving a file, I'm around 11 seconds. If I take the time to shut down Unity, and re-open it, my compile time will reset to about 3 seconds again. But tomorrow it'll be up to around 5... then 7 or so... and in a few days it'll become unbearable and I'll need to restart Unity again. I've tried googling this problem. The issue is Google is trying to be SO helpful that I get pages upon pages of hits on how to speed up my compile times using Assembly definitions. Yes, thank you Google. I already know that. Almost all those links are highlighted as visited, because I did all that a few months ago. While I was doing that original research I do remember seeing people complaining about this exact issue, and that restarting Unity would (temporarily) clear it up. Thats how I knew to try a restart. Anyone know why this happens, and if there's an easier/faster way to stay on top of it, aside from a restart? I'm using AsmdefDebug, and it's telling me that of my last 11.93 second compile: myAssembly.dll is .58s Assembly-CSharp.dll is .43s And Assembly Reload Time is: 10.918s It's the assembly reload time that keeps creeping up. Any help?