Verma has mentioned above much of what I have seen or experienced so far playing with RAMDisk software (which admittedly is not a whole lot.) The ones that I had looked at a while back had free options and then paid options. The free options had limited total RAMDisk size (4 GB is most common) and may lack some of the options such as being able to write that data back to a storage drive to save the state during system shutdown or startup. With the full paid versions of the software, however, you could create much larger RAMDisk drives if you have the memory capacity to support it.
Since RAM by its nature will lose all data when it is powered down, the software should have an option to save that data back to the hard drive of your choice IF you need to save the data. If you are only moving temp file folders then you don't need to save the data and it can just be lost when the system shuts down. This means there is no hit to your startup or shutdown times. However, if you do wish to save the data, everything must be transferred, so the more data you have in your RAMDisk, the longer that is going to take to write back or read from your drive.
RAM operates at much greater throughput than even several SSDs in RAID 0, so it makes sense that a program which is going to be needing that sort of throughput for small data would benefit from moving it to RAM. However, at least with most of the instances that I played with, it is best to use it more for temp space or as a scratch disk space than for permanently running full programs or persistent data within. For example, the situation that I tested this all out with was for use as a scratch disk for design workstations. Within the Adobe software you can configure your preferences for scratch disks (which one to use first, the amount of space, etc.) I created a 4 GB scratch disk in RAM on a workstation with 16 GB of total memory available. On most any smaller sized project the performance was amazing. However, once you started working with much larger files or complex designs with a lot of effects and file history, then the scratch disk became full and temp files would then also be pushed to the hard drive, which basically meant that you now were only getting the throughput of your hard drive speed and not the RAMDisk.
Other software didn't work quite as nicely with the scratch disk on the RAMDisk drive simply because of limited capacity. In another application they used called Flexi, you can set up your destination for temporary files and scratch disk, and while 4 GB of temp space was enough for most files, if you have Adobe open and Flexi open both using the same 4 GB of scratch disk it quickly fills up. The down side to this is Flexi is not smart enough or capable of using a different location or hard drive for additional temp file space. Once the RAMDisk space is full, the program crashes.
So, long story short, if you have a ton of RAM and only need 4 GB of space for your RAMDisk and never need anything more, then it may be a good fit. If you need more space than that and buy the software versions that allow for larger RAMDisks then even that should be good. But like everything there are limitations and it may not work for everything or in every situation. It's hard to say or recommend until we knew a little more of your specific situation and planned usage of it. If it is only for browser caching then I'd say it may not be worth it. Performance-wise your SSD will offer more than enough throughput and you will really be limited by the speed of which your internet, network, etc. will transfer the data. The only reason for moving it would be for eliminating the possible wear on your SSD which was also mentioned above.