On Tue, 11 Jul 2017, Jaromil wrote:

> On Tue, 11 Jul 2017, Ivan J. wrote:
>
> > This seems okay. I reckon it would also allow the machine running
> > amprolla to use less disk space as the repository (/merged) would
> > not have to be generated in a 3-directory rotation scheme, but it
> > could rather be done on the mirrors. Does rsync pushing allow for
> > command execution remotely?
>
> do anyone has a rough estimation of the space needed for this "mirror
> provider" functionality?
>
> I presume it can be done for both jessie and ascii, if yes then better
> include both in the estimation.
>
> thanks

Currently my instance of amprolla is merging all possible repositories
and architectures: jessie, ascii, and unstable.

There's a spool directory where all the raw unmerged files from all of
the repos are being held and downloaded. It amounts to 2.2G

Then there's three merged directories in rotation, all of which are also
2.2G, give-or-take.

It amounts to 8.8G.

These three merged directories are in such a rotation to avoid downtime
when the actual merge is being performed. The logic can be found here:
https://github.com/parazyd/amprolla/blob/master/orchestrate.sh

If you are asking this because of hardware necessities, I'd say the
minimum viable machine would be a dual-core CPU, 2GB of RAM and 20GB
storage space.

--
~ parazyd
GnuPG: 03337671FDE75BB6A85EC91FB876CB44FA1B0274
GnuPG: https://parazyd.cf/FA1B0274.asc