I hate to say this, but it depends, @Michael Enslein 😮😮😮
First, I suppose you're doing the lookups in CT (not in Excel). I have done both and it works like a charm. We have about 700 apps. Is this sizable? I guess it depends. Neither Excel nor CT have a problem with such lookups.
Your vendor table might be what you call sizable. How big is that: 10,000 rows? 50,000? More?
In CT, we do lookups to and from our server table, that has about 35,000 rows. For instance, we validate whether a server-to-application relationship points to a live server. This is a lookup into the server table. We have noticed no particular performance issues.
Also, we look from the server table (again, 35k) to find out the application a server relates to. Again, no issues.
In Excel we sometimes try things, and in such cases we might combine tables like above. I don't recall whether we have used the server table, but I cannot imagine Excel having an issue with large cross-lookups.
The only issue we have stumbled upon now and then is the dreaded cyclic reference error. I wrote about this for the TBMC2020 hackathon (A Midsummer TBMA's Dream). I learned recently that CT will show you tables that relate to each other:


However, it doesn't detail the nature of the relationship.
In my proposal/demo I explained it would be useful to find such cross-lookups, heavy-hitting functions (LookupEx / SplitEx / SumIf), etc.
I'll revisit the 2020 article to see what I come up with (e.g. an enhancement request).