esanisa
09-04-2014, 11:24 PM
Hi, I'm aware that if I have a huge database (2TB or more), I've moved the whole database into another virtual database-only machine on the internet, which runs CentOS 6.x and postgresql 8.4 in a datacenter.
I've shared this database to a group of my friend and can have a BUG daily increasing of hands and Caddy Notes (Badges).
But I have 2 things for suggestion:
1. DatabaseParentFolder in settings should be configured if you are not using localhost as your database IP address.
2. If DatabaseParentFolder is movable and indexable in the database, why should we put the data in folder?
I've done a lot of job to save the disk and maintain the database well. But if you are having about 1M+ players data, the ParentFolder is still a HUGE costly for both users' computer performance if you are not using the postgre served locally.
I've shared this database to a group of my friend and can have a BUG daily increasing of hands and Caddy Notes (Badges).
But I have 2 things for suggestion:
1. DatabaseParentFolder in settings should be configured if you are not using localhost as your database IP address.
2. If DatabaseParentFolder is movable and indexable in the database, why should we put the data in folder?
I've done a lot of job to save the disk and maintain the database well. But if you are having about 1M+ players data, the ParentFolder is still a HUGE costly for both users' computer performance if you are not using the postgre served locally.