qa_pcbnew profiling results

[Sylwester Kocjan]

Hello!

I was wondering why pcbnew tests take so long time and I ran gpof on them. Sadly, I don't know what can be improved without in-depth knowledge of architecture. Let me share the results, maybe someone will find it interesting.

Best regards,

Sylwester

[Seth Hillbrand]

Which tests are you referring to?  Do you mean that running DRC on a specific board takes a long time?  Or do you mean that running `make test` takes a long time in the KiCad codebase?

If you mean the former, you will need to open an issue report and attach the specific board.

If you mean the latter, this is a known problem but without an adequate solution.  We need to open many, many boards and run checks to ensure that software updates do not regress prior solutions.  Each board load takes a fair amount of time.

Seth

Seth Hillbrand

Lead Developer

+1-530-302-5483‬

Long Beach, CA

www.kipro-pcb.com    in...@kipro-pcb.com

--
You received this message because you are subscribed to the Google Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to devlist+u...@kicad.org.
To view this discussion on the web visit https://groups.google.com/a/kicad.org/d/msgid/devlist/daf16fd424ef482f8b5261e49aab235f%40grupawp.pl.

[Sylwester Kocjan]

Hi Seth,

I mean the latter (i.e qa_pcbnew) and I wanted to find out which functions take so much time. It turns out that it's R-tree, clipper library, even shared_ptr.

BR,

Sylwester

To view this discussion on the web visit https://groups.google.com/a/kicad.org/d/msgid/devlist/CAFdeG-r%2BeLbhd%3DnC8-qY-O9Q46mbxhYf1gBuKxnNyKRC4vmMnA%40mail.gmail.com.