Fri Mar 26 08:35:01 PDT 2010
- Previous message: [Slony1-general] Slony performace issues and an idea
- Next message: [Slony1-general] Slony performace issues and an idea
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ariel Wainer wrote: > I'm having some performance (I/O) issues. I've been thinking about > putting the tables slony uses to log events on a different tablespace > located on a ram disk. What do you think of this approach? Is it > possible or convenient? Slony/Postgresql won't know that the disk you move your slony tables is a RAM disk, so in that respect it will 'work' The problem is that you need to consider what will happen when your server fails/reboots/kernel panics etc.. If you lose the RAM disk you won't be able to recover the slony on that node. You have to think about if your situation will allow you to live with this. The other thing to remember is that even if you move the slony log tables to your RAM disk your WAL log will still be on your normal disk, I can't really say what the actual performance increase will be (feel free to post any benchmarks you collect during your testing of this) > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general -- Steve Singer Afilias Canada Data Services Developer 416-673-1142
- Previous message: [Slony1-general] Slony performace issues and an idea
- Next message: [Slony1-general] Slony performace issues and an idea
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list