Another Interesting Question - Maybe has an obvious solution - but still interested.
Let's assume you have a customer community which allows self registration and social sign on (facebook, google as Auth Provider). You have over 25K customer expected to sign up on the day of the launch, and they DO NOT have person accounts enabled.
In the login settings for the community, you have specified an 'Parking Account' where all the contacts get added to this common account record.
What would be the optimal solution so that you avoid the 'Account data skew' as described in this document.
It helps, the reason it is suggested to use a User with no role or with the only role of an hierarchy is because it prevents extra processing for sharing to the records and related records. But it only goes so far and you should be prepared to see decreased performance for the user around the benchmark either way.
I'm choosing my words carefully here, prepared for it, not expect it, decreased performance not poor performance, around the benchmark not at it.
