Performance notice

[lmProgramming]

Hi, I can see that it works as intended. I was very happy and started refactoring my code, but then I actually compiled my code and saw that the compilation time jumped from ~0s to ~20s. Unless I am mistaken and did something wrong, it would be very nice of you to note it in the README, that this patch can and probably will impact compilation time strongly. Currently, I had to revert the patch to continue work on my project

[lmProgramming]

But just wanted to say, great work! Everything else was working perfectly

[lmProgramming]

Tested with Unity 6000.3.4f1 and Rider 2025.3.2

[kandreyc]

Hi mate!

Sorry to hear that you ended up with such an issue related to compilation time. Anyway, thanks for your feedback.

I remember that I faced this issue some time ago as well and even did some fix to avoid it. I will keep this issue open and try to find the reason of that.

Few questions to you, that might help me during investigation:

1. You had only 1 .asmdef with csc.rsp file, or many of them?
2. Where that .asmdef/s with csc.rsp file/s are located? e.g inside the project, or packages
3. Is it a big project? I mean is there a lot of packages with code in use?
4. Is there a big code base on your side?
5. Is the project running under SSD?
6. Is it a constant compilation time? If you will perform one more change in code, will it take the same amount of time to compile?

[lmProgramming]

Hi,

Thanks for replying!

1. I put 1 csc.rsp file in each of the 16 assemblies.
2. All inside Assets/Scripts
3. Packages - mostly default ones
4. Hm, despite the assembly count, not really yet. 7702 lines of code in the assemblies
5. SSD
6. It took 20 seconds compiling change for 1 assembly. For multiple assemblies, it looks like it only took a second more? Interesting

Here's the project with the branch where I experimented with your patch: https://github.com/lmProgramming/space-pixel-unity/tree/build/unity-csharp-patch