# VDS High on Server CPU ve RAM How to Analyze Use?

https://www.nettescil.com.tr/knowledgebase/article/vds-high-on-server-cpu-ve-ram-how-to-analyze-use

Virtual Server infrastructure VDS High on Server CPU ve RAM How to Analyze Use? Most often require multiple adjustments to be evaluated together. The following problem solving protects the current situation first, then measure the result.

Menu names may vary according to the version used. Therefore, write the target on the screen, the service to be affected, and the expected value after processing before the start. Apply the security settings gradually with the network to not lose the console access and employee services.

## Before the process starts

- List the areas to be recorded on the panel before processing.
- Note that existing errors and alerts are not mixed with new results.
- Test access to backup storage location.
- Select the second method to make the final control.

## Step by step app

1. Save console access, network configuration, backup status and existing service list.
2. Upgrade packages with operating system to security updates and check time synchronization.
3. Create separate user for management; apply strong authentication and minimal authorization approach.
4. Simply open the really used ports on the firewall and test the rule without closing the current session.
5. Review disk, memory, processor, inode and network usage with time range instead of instant value.
6. After changing, verify the service status, rested ports, logs and external access.

## Verification and troubleshooting

The response code should be evaluated with time and content. For example, HTTP It should not be considered successful in the queue, which appears to be delivered to an empty page or 200 rotating, but the remaining message on the tail should not be accepted.

- Does the content of the response carry the expected data?
- Is the process time in normal range?
- Is there a job waiting on the tail?

## Safety and continuity notes

Temporary test files, open debug mode and wide allowlist records should not be forgotten after the transaction. Add clearly the removal of them to the final checklist.

Return to the final successful situation instead of adding new settings in the unforeseen situation. Check the records at the trading time and repeat the same test with one variable.

## Frequently Asked Questions

### When should I open support request?

Stop new trials if there is unopened error on logs, data integrity risk or access loss; ask for support with time stamp and masked evidence.

For similar content [Virtual Server Information Bank](https://www.nettescil.com.tr/bilgi-bankasi/sanal-sunucu) You can review the section.