2 ms·
Why not just move the logging table into a different tablespace/file group and place this on a different disk? That would fix write performance problems.
by chris_wot 15y ago
Why not just move the logging table into a different tablespace/file group and place this on a different disk? That would fix write performance problems.
- AlisdairO 15y agoThis is absolutely a good thing to do, but it doesn't make you safe - the disks running the database's redo logs are the ones that get hammered in a logging scenario (since the writes to the table and indexes are largely appending, and don't have to be written to disk to commit a transaction). These logs are usually global to the DB instance, so you can't easily (to my knowledge) separate them out. This being the case, they can significantly affect the performance of the rest of your system if too much logging starts happening.