Most of the general tweaks assume you have a system with one physical hard drive. Others depend on your system configuration and what kind of software you use. For example if you have multiple physical hard drives(not just multiple drive partitions) then you may benefit from optimizations such as, putting your page file on a different physical drive than Windows. Putting your input or Gozinta data on a different physical drive than your output or Gozouta data. The last being if you crunch large databases constantly, or perhaps you process huge video files.
The more independant drive heads you have seeking simultaneously the better, in the case of conventional HD storage. Newer solid state storage is another matter. Most likely the SSD would hold the OS.
All the page file configuration schemes would depend on the physical ram in your system and how you use it. I don't want to get into arguments about the "optimal page file size" for a PC with x GB ram. Especially since there is no such number. It depends on how you use it.
Myself I like to use what I call "light weight" defraggers to reduce disk fragmentation in a short amount of time. Also, generally speaking, if possible it's better to run conventional HD with a majority of the space free. In other words, it's a good idea if you have more than 50% free disk space before you start processing stuff. Of course if you are processing video, it's going to use up lots of this space. But when you get done, eliminate temp files, and move the video off to some other medium(maybe an external drive or burn to disc) then things should settle back down to lots of free disk space.
The main optimization is your mind. Watch your system. Listen to it. Keep a feel for how it runs when you try this scheme for awhile vs. that scheme. Whenever I'm working with equipment I try to be aware how it feels. If it's sluggish, laboring, smooth etc..
You don't necessarily have to run benchmarks to know what's going on. If you are tuned to your equipment you should have a good feel what runs rough and what runs smooth. The fact your are on a PC located on your desk or work bench is a big advantage compared to working a terminal connected to a mini-computer that may be in another building. With the terminal setup you only have lags in response on the screen as a physical indicator. With your PC tower right there where you can see it and hear it, you have lots of visceral feedback.
Of course you need starting points for things to try.
The above examples are general of course, since I know nothing about your PC. But in my experience, the most effective optimizations are possible when you have knowledge of the input. In other words, I can read an 800 MB text file looking for a string of 8 zeroes... or, if I know that the string, if it exists, is only on line 7, then I can just go to line 7 and read it, then look for the zeroes. If you have a PHD your might call 'em heuristics. I call it knowing what you're looking for.