I've got a web project that pretty much consists of three parts: Code, Assets and Cache.
I'm thinking of splitting it through multiple drives - Put my whole Code into SSD partition, Assets onto big HDD and Cache, which has many I/O operations, into Ram disk. Does this setup make sense?
If so, should I adjust my partition table to handle this configuration or using ln will be sufficient?
Sounds to me like too much complexity. That might just work against you and decrease performance, of yourself and of the software (incorrect setup for example).
I would just put together a raid10 (using a hardware controller or mdadm, see for example: How to create a bootable redundant Debian system with a 3 or 4 (or more) disk software raid10?) for all data which needs to be retained and use a ramdisk for data which can be deleted because of a reboot. You could use /dev/shm for that, it's a ramdisk that comes with linux by default, fills up to about half the RAM size (that's configurable) and dynamically expands and shrinks depending on need.
Regarding using symlinks, that to me sounds like a good idea. It requires the least reconfiguration. Just move the data, create a symlink and it should still work as before. The only catch in my experience is when you use a chroot environment, then you of course have to move the whole chrooted environment and not just the data.
Yes. You will have a very fast and optimized system.
Altough there are cases, when it is ok, and there are cases with alternative priorities (f.e. if you have only a very little budget for the hardware).
