I use SectionedFetchRequests to show my CoreData in ordered lists grouped by some criteria, as Paul explains here: https://www.hackingwithswift.com/books/ios-swiftui/sorting-fetch-requests-with-sortdescriptor

In this article he says: "Having a second or even third sort field has little to no performance impact unless you have lots of data with similar values". But...

This is one of my requests:

@SectionedFetchRequest(sectionIdentifier: \.classWeekDay!, sortDescriptors: [SortDescriptor(\.classWeekDay), SortDescriptor(\.classHour), SortDescriptor(\.classMinute)]) private var students: SectionedFetchResults<String, Student>

It sorts my students, consecutively, by their class day, time hour, and time minute. And group them on its weekDay. It works like a charm on my iPhone 14 Pro, and even on an iPhone 7. But when building XCode project, it takes long time, making even coolers fans speed up for a while, like making a great effort until it finally compiles. Only whit three criteria: not with two.

Is this normal? Is this the correct way to do so?