VACUUM does not have a direct impact on read/write performance since it only remove files no longer referenced by a Delta table ( unless your data volume is so high that you are hitting the read limits of underlying S3/GCS/ADLS buckets ) . It would make sense to run it as a separate job scheduled daily and potentially using sport instances

VACUUM has no effect on read/write performance to that table. Never running VACUUM on a table will not make read/write performance to a Delta Lake table any slower.

If you run VACUUM very infrequently, your VACUUM runtimes themselves may be pretty high, so it is suggested to run VACUUM somewhat regularly. How often you should run VACUUM depends on your storage costs.