Number of physical reads: <count>
A large number of physical reads are taking place on the volumes of the database as the data requested by the applications was not found in the data cache.
If a table is accessed for the first time, or if it has not been used for a long time, and was therefore displaced from the data cache, then this situation is not a problem.
However, if this does not explain the read activity, you should check the hit rate for the data cache, and increase the size of the data cache, if necessary.
Make sure that the SQL statements specified by the application do not read significantly more data than is necessary for processing, because of poor search strategies, for example.
If the special database parameter UseDataCacheScanOptimization has the value yes, then table scans use only 10% of the data cache for caching the table. This means that the table cannot be held completely in the data cache, and the next scan has to read it physically again.