This whole ramdisk idea seems weird to me. Normally I would expect an app to write things to disk swap space when there is not enough RAM to store data. Now you guys are trying to reduce the amount of RAM that's directly available to the app, and ask it when it feels there is not enough of RAM, write things to the RAM disk? This only makes sense when the directly accessible RAM to PI is limited, so you use the remaining RAM as RAM disk. Is this the case? Do I miss anything?
Another thing that I have been told is that OSX makes good use of RAM. When the system needs to write a page file, it will first check whether there is RAM available. If yes, it writes to the RAM rather than the disk. So the general advice is not to use RAM disk for the system. This is for the system. I am not sure whether this applies to apps.
The original complain about PI here is the program loading time. I think the only reasonable solution to this is to use an SSD as a boot disk and system disk. If Carlos indeed has an SSD in his iMac and the loading time for PI is still painfully slow, then something is seriously wrong, and this almost should have nothing to do with RAM disk.
My 2 cents.
Cheers,
Wei-Hao