Does Guid PKs have any performance impacts?

[snax4a]

Hi guys,
I wonder if you are using GUID PKs in all your applications and if you had ever any performance issues with that?

In one of my projects, I used GUIDs as PKs and I noticed some performance issues when using EF Core and making a lot of JOIN queries.

I have read some discussions and articles regarding that question:
https://stackoverflow.com/questions/11938044/what-are-the-best-practices-for-using-a-guid-as-a-primary-key-specifically-rega
https://www.sqlskills.com/blogs/kimberly/guids-as-primary-keys-andor-the-clustering-key/
https://web.archive.org/web/20120812080710/http://databases.aspfaq.com/database/what-should-i-choose-for-my-primary-key.html
https://blog.bitsrc.io/why-is-nanoid-replacing-uuid-1b5100e62ed2

However, on a small-sized application, I thought it shouldn't have any noticeable impacts so probably my generic repository pattern implementation or LINQ queries are not the best.

I would like to know what is your experience with GUID PK performance with many JOIN queries and if you have any plans in extending the boilerplate to contain a more complex service method that loads data with Include, ThenInclude efcore methods.

Maybe someone has already forked this project anded some more complex repository queries?