On one of my main computers I replaced two RAID0 7200 RPM SATA II drives with two RAID0 solid state drives (rated at 260MB/s seq read, 180MB/s seq write).
SlickEdit screams. No pauses or hiccups.
(Common Sense Warning: Your Mileage May Vary, Don't Quote Me, etc).
On the one hand, this is great (SE is not why I got the SSDs, but it is a great perk).
On the other hand, it cost me $1,400 so it's not a general solution.
The SlickTeam is working on threading to push more stuff into the background to avoid blocking the foreground. IO profiling might help things that still need to happen in the foreground. IO profiling might even turn up non-optimal IO patterns in unexpected places. It seems large vtgs are often assumed to be the reason for slowness, but it seems like a btree ought to be able to perform extremely well at any size unless it is serving up unindex/unoptimized linear scan queries. Anyway, IO profiling might reveal other non-vtg places where tweaks could boost performance. Just a thought.