Closed
Bug 454414
Opened 16 years ago
Closed 16 years ago
Postgresql reconfiguration
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
0.6
People
(Reporter: lars, Assigned: aravind)
References
Details
According to Josh Berkus of PostgreSQL, three quarters of our performance trouble relates to disk access. The Transaction log and the database should not be on the same physical disk drive. Aravind suggests iSCSI, because of complications in adding disk space to the physical machine. Josh suggests to putting the database on iSCSI and the transaction log on the local drives.
Updated•16 years ago
|
Target Milestone: --- → 0.6
Comment 1•16 years ago
|
||
Aravind, is this done, or is there more to do with configuration?
Comment 2•16 years ago
|
||
Aravind, is this done or is there more to do with configuration?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•16 years ago
|
||
Its done. We write transaction logs to local disk, and data to the remote iscsi disk.
Comment 4•16 years ago
|
||
Ok, leaving as resolved. Thanks.
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•