To increase the access speed of your swap space place it into a RAM disk.
I worked on a system that did this, in the 80s.
We had three IBM mainframes, one 370/168 that was only used for batch processing, one that was used for a realtime control system (that might have been a 3033), and a third 370/168 that was split between interactive use (TSO) and batch use. The interactive machine had about 500 terminals attached to (3277 and clones), and at peak times (weekdays 11am or 2pm), most terminals were in use. Due to the realtime control system using a lot of bizarre and older code, we could not use XA, so the interactive machine had only 16 MB of address space, and only that much memory. It was quickly found that at peak times, it was swapping rather badly, which made performance somewhat awful.
The solution was to not swap onto disks (we also had only 3350s, as the 3380 was infamously delayed), but instead buy a RAM disk. We managed to get a 144 MB RAM disk from some Japanese vendor (Hitachi? Fujitsu?) that was IBM channel compatible, and interactive performance was great again.
By the way: We had 500 users sharing a roughly 5 MIP machine with either 16 or 160 MB of RAM (depending on how you count), and interactive (CLI) performance was just fine. We edited code, used compilers and linkers, ran small programs, submitted and checked batch jobs, used it for e-mail, and ran interactive data analysis tools (about 50 terminals had Tektronix 4014 attached for graphics). One of the reasons this worked was that the CPU (the 5 MIP one) didn't have to deal with disk IO, tapes, terminal IO, keystrokes, or any of that, since that was done using channel processors. We also had a lot of disks attached (about 100 or 120), so there was lots of IO parallelism. Today, people insist of having a multi-gigahertz machine with gigabytes of memory for interactive work.