I can report no impact to performance at a far lower limit - my contact named "Telemarket Spam" to which I add callers and block that one contact is around 50 phones deep.

I would add all the numbers to one contact to simplify your life until you notice an issue or a problem and then back off a bit, and iterate to multiple contacts.

At some point, if the annoyance of curating this list overcomes my hesitance to subscribe to a service that integrates with the iOS phone app to classify and attempt to block suspect and known bad actors, I'll probably pay for a service to block calls. So far, I can't measure any slowdown or freeze - but I could see potential issues if you do manage to have thousands of numbers in the same contact.

Sorry this isn't super rigorous, but this one might be fairly easy to test empirically by generating a contact with 5,000 numbers and seeing when it breaks when you have time and a backup to restore your iOS device.

If I needed to profile this, I could use Instruments to attach to the contacts app and see where the contact is stored on the filesystem (for iOS or macOS) so there's clearly a way to reverse engineer how much space a number takes to store and measure any CPU usage related to editing that file or processing that data. Unless you see memory and CPU spiking, you can probably safely assume that as long as you care to keep adding numbers, the system will respond well if you just look at overall speed of the device while editing that contact.

I can report no impact to performance at a far lower limit - my contact named "Telemarket Spam" to which I add callers and block that one contact is around 125 phones deep.

I would add all the numbers to one contact to simplify your life until you notice an issue or a problem and then back off a bit, and iterate to multiple contacts.

At some point, if the annoyance of curating this list overcomes my hesitance to subscribe to a service that integrates with the iOS phone app to classify and attempt to block suspect and known bad actors, I'll probably pay for a service to block calls. So far, I can't measure any slowdown or freeze - but I could see potential issues if you do manage to have thousands of numbers in the same contact.

Sorry this isn't super rigorous, but this one might be fairly easy to test empirically by generating a contact with 5,000 numbers and seeing when it breaks when you have time and a backup to restore your iOS device.

If I needed to profile this, I could use Instruments to attach to the contacts app and see where the contact is stored on the filesystem (for iOS or macOS) so there's clearly a way to reverse engineer how much space a number takes to store and measure any CPU usage related to editing that file or processing that data. Unless you see memory and CPU spiking, you can probably safely assume that as long as you care to keep adding numbers, the system will respond well if you just look at overall speed of the device while editing that contact.

I can report no impact to performance aa a far lower limit - my contact named "Telemarket Spam" to which I add callers and block that one contact is around 50 phones deep.

At some point, if the annoyance of curating this list overcomes my hesitance to subscribe to a service that integrates with the iOS phone app to classify and attempt to block suspect and known bad actors, I'll probably pay for a service to block calls. So far, I can't measure any slowdown or freeze - but I could see potential issues if you do manage to have thousands of numbers in the same contact.

Sorry this isn't super rigorous, but this one might be fairly easy to test empirically by generating a contact with 5,000 numbers and seeing when it breaks when you have time and a backup to restore your iOS device.

If I needed to profile this, I could use Instruments to attach to the contacts app and see where the contact is stored on the filesystem (for iOS or macOS) so there's clearly a way to reverse engineer how much space a number takes to store and measure any CPU usage related to editing that file or processing that data. Unless you see memory and CPU spiking, you can probably safely assume that as long as you care to keep adding numbers, the system will respond well if you just look at overall speed of the device while editing that contact.

I can report no impact to performance at a far lower limit - my contact named "Telemarket Spam" to which I add callers and block that one contact is around 50 phones deep.

I would add all the numbers to one contact to simplify your life until you notice an issue or a problem and then back off a bit, and iterate to multiple contacts.

At some point, if the annoyance of curating this list overcomes my hesitance to subscribe to a service that integrates with the iOS phone app to classify and attempt to block suspect and known bad actors, I'll probably pay for a service to block calls. So far, I can't measure any slowdown or freeze - but I could see potential issues if you do manage to have thousands of numbers in the same contact.

Sorry this isn't super rigorous, but this one might be fairly easy to test empirically by generating a contact with 5,000 numbers and seeing when it breaks when you have time and a backup to restore your iOS device.

If I needed to profile this, I could use Instruments to attach to the contacts app and see where the contact is stored on the filesystem (for iOS or macOS) so there's clearly a way to reverse engineer how much space a number takes to store and measure any CPU usage related to editing that file or processing that data. Unless you see memory and CPU spiking, you can probably safely assume that as long as you care to keep adding numbers, the system will respond well if you just look at overall speed of the device while editing that contact.