2010 C3d

You can mitigate the swap problem somewhat by tweaking virtual memory and by placing the swap file on a separate hard drive so that it remains one contiguous section.

That's often a waste of a hard drive. That is especially true if you are running a 64-bit OS and you have 6GB or more of RAM. C3D is still a 32-bit application, and it is limited on the amount of memory it can access. So if you have 6GB of RAM, you'll hardly be touching your pagefile at all, and you can completely forget about it.

On the other hand, if you are trying to run C3D on a machine that has 2GB or less of RAM, you can notice a significant improvement if you have your pagefile on a dedicated drive. Although you would get even more bang for the buck if you took those two hard drives and used them in a RAID0 array instead, then set your pagefile to a set size and make sure it doesn't get fragmented. Best way to do that is to set it to 0 first, then set it to the size you want. This will create the entire pagefile all at once, and it shouldn't be fragmented (unless your drive is already pretty full and fragmented).