@Naveenkumar1811 Since your silver is a streaming job, there can be lots of files and metadata being created based on your write interval and frequency of new data. If there are more files being created in few mins, it potentially leads to small file issue and in this case your read speed will be affected. Try to optimize and Vacuum and see if you can note any difference in read. If you find a difference, you can regularly optimize this table by scheduling a job for it, or you can also test with liquid clustering which handles this scenario a bit effectively.

Try to Read more on Vacuum and the retention policy before executing it.