Is Nestedset effective on big data?

Question

symfony

Colleagues, good evening!
Who has experience with the attachment storage model, Nestedset?
I have a task in TK.
5,000,000 organizations.
Each organization has its own services.
Services are grouped.
Example:
---------------------------------
Vehicle Maintenance (Group)
---Oil Change
---Diagnostics
- --Replacement of brake pads Looked
closely at the Nestedset storage model in order to group services.
A kind of category, but only services.
As far as I know, TreeLeft and TreeRight are recalculated each time a record is added.
I'm starting to create services and link them to organizations.
I assume that by 100 thousand there may already be problems, with a long calculation.
Should I use Nestedset ?

Answer 1

nested sets is suitable when the insertion of elements will not be frequent
For example, it is suitable for a referral system - users do not register very often, and the page with referrals is updated almost every second.
Surely someone wants to export services from an excel file with a bunch of records.
I think closure tables will suit you
https://habr.com/ru/post/263629/