At the moment, the postgres storage is the most expensive factor in our billing and by a large margin.
We should try to cut down these costs by down-scaling the storage size of the database. This can be done by setting the storage parameter in the manifest, see here. Note that the default parameter apparently is not 10 GB as written down in the documentation but 50 GB.
Furthermore, we should configure our squids to be deployed on dedicated instances instead of 'collocated' development machines.
TODO
Set the storage parameter to 10 GB and see if the squid still works as expected. Should be tested on Amplitude as it has the most blocks.
Set the dedicated parameter to true for all squids.
At the moment, the postgres storage is the most expensive factor in our billing and by a large margin. We should try to cut down these costs by down-scaling the storage size of the database. This can be done by setting the
storageparameter in the manifest, see here. Note that the default parameter apparently is not 10 GB as written down in the documentation but 50 GB.Furthermore, we should configure our squids to be deployed on dedicated instances instead of 'collocated' development machines.
TODO
Set the storage parameter to 10 GB and see if the squid still works as expected. Should be tested on Amplitude as it has the most blocks. Set the dedicated parameter to true for all squids.