Hi,
I don't know which tool(s) you're using and whether they have any monitoring capabilities. So here are some general remarks:
Your data cache has a filling level of 99,5%. This is not an issue as caches are intended to hold data. Data is read from disk and put into data cache. And if your system is running for some time your cache will become full. If more data is read from disk, some old data is removed from cache. (Old data means data that has not been touched for a long time).
So from the pure percentage you cannot derive that your cache is a bottleneck. Important is the cache turnover; so if your cache content is replaced frequently this might be a bottleneck.
From your description I would guess that saptempdb could be a bottleneck. If you have some space you can increase it.
For a more detailed and substantial analysis you require a monitoring.
As a simple (to execute) approach I like to start with is sp_sysmon monitoring. This runs for a certain time and collects a lot system information but it is not easy to read and understand. Here is a link to the documentation:
Performance and Tuning Series: Monitoring with sp_sysmon - SAP Library
Maybe you can run it once (during a period of high system load) and post the output into this scn thread.
sp_sysmon writes the results to your sql console. The run-time is given in the format 'hh:mm:ss'. So a data capture for three minutes looks like this:
sp_sysmon '00:03:00'
go
Some counters in sp_sysmon are not resetted so that it does not influence other monitoring. If you don't have other monitoring or if it does not matter to reset counters, you can run sysmon with the clear option:
sp_sysmon '00:03:00', clear
go
Best regards,
Juergen