There's certainly enough configuration files that a few tweaks can make the system seem a little more responsive: the
IBM Redbook on the Linux *kernel* has many optimizations that can be applied. Using a different file system can reduce load on the cpu and that can be configured as well.
Many kernel parameters can be affected in the /etc/sysctl.conf file - I like:
vm.swappiness = 90 # Could even go to 100 for snappy user response at the expense of throuput.
vm.dirty_ratio = 35
vm.dirty_background_ratio = 15
net.core.rmem_default = 8388608
net.core.rmem_max = 8388608
net.core.wmem_default = 8388608
net.core.wmem_max = 8388608
net.ipv4.ipfrag_low_thresh = 262144
net.ipv4.ipfrag_high_thresh = 393216
net.ipv4.tcp_rmem = 4096 87380 8388608
net.ipv4.tcp_wmem = 4096 87380 8388608
as a starting point while the large aerospace company I work for has many other tweaks for reducing network traffic. Ext4 with "relatime,commit=50" helps the filesystem if you have a reliable power backup while an SSD hard drive for booting the kernel is certainly faster. This is assuming you have enough hardware (memory, fast h/d, etc.) for the tweaks to make a difference. There is no single "George Jetson" button...
-LouieLouie