Another option which is growing in popularity is distributed in memory cache. There are quite a few companies providing such technology.
Pricing can range from free to quite expensive.
One recommendation with these technologies is to test them under heavy load conditions.
Good luck.
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Moreno Andreo
Sent: 29 July 2016 10:19
To: pgsql-general@postgresql.org
Subject: Re: [SPAM] Re: [GENERAL] WAL directory size calculation
Il 29/07/2016 10:43, John R Pierce ha scritto:
Aside of this, I'm having 350 DBs that sum up a bit more than 1 TB, and plan
to use wal_level=archive because I plan to have a backup server with barman.
With that many databases with that so many objects
350 DBs with about 130 tables and a bunch of sequences each, for the sake of precision.
With extensive use of BLOBs.
and undoubtable client connections,
Yes, that's another big problem... we run normally between 500 and 700 concurrent connections... I had to set max_connections=1000, the whole thing grew up faster than we were prepared for...
I'd want to spread that across a cluster of smaller servers.
That will be step 2... while migration is running (and will run for some months, we have to plan migration with users) I'll test putting another one or two machines in cluster, make some test cases, and when ready, databases will be migrated on other machines, too.
I posted a question about this some months ago, and I was told that one solution would be to set the servers to be master on some databases and slave on others, so we can have a better load balancing (instead of having all writes on the sole master, we split among all masters depending on which database is getting the write command, especially when having to write BLOBs that can be some megabytes in size).
I don't know to achieve this, but I will find a way somewhere.
just sayin...
ideas are always precious and welcome.
--
john r pierce, recycling bits in santa cruz