It's highly unlikely. The point source table is indexed or hashed I believe so searching should scale pretty well independently of the number of entries. PI Server performance in general is a huge topic. Is there a particular performance issue you are running into?
If you are interested though, here is a reference, but please take note of the caveats mentioned.
KB01008 should come with some extra notes, like what happens if pointDB_RemoveEmptySource doesn't exist in your Tuning Parameters and even technical support via a remote session can't enable it
Try this with piconfig:
@istr name, value PointDB_RemoveEmptySource, 1
After creating this parameter I had to completely restart the PI server (tried restarting the base subsystem but a full restart worked).
Thanks for the piconfig command which will help me out to carry out piconfig if tunning parameter doesnt work out. It was informative.
Thanks for the KB article. I was just wondering if I clean up my Point Source table will it improvise some part of PI system. Because some where or so by applying such tuning parameter would reflect changes in PI System which in-turn will have a better structuring in the system. So was looking for any performance improvement. But your point of index searching was informative. Thanks.\