CrimsonDX, did you see the reply to your question on the GlowWorm forum at poseworks?   It seems GW users have reported measurable benefits from using GW.   As I said, GW wasn't the solution for me the other day, but you may find it does the trick for you.   For the record, Poser can quite quickly grab 1Gb of RAM when rendering.   More memory won't do any harm, but there is a physical limit as to how much Poser will ever exploit in its current form.   I think it is a theoretical limit of 2Gb, on the basis of the addresses it is capable of handling, but a practical one of 1.2 to 1.3.  

One thing I have tried is to start Windows Taskmanager just before rendering (and stopping everything else, Poser excepted).   Apart from closing Poser, the only thing that seems to prise memory away from Poser is to minimise it.   It uses a lot of memory for merely being visible.   After kicking off a render (which had previously failed umpteen times), I used Taskmanager to minimise Poser.   That recovered enough memory for the render to complete, I believe.   Minimising by clicking the box at upper left  tends to be less successful.