X server issues and ports
Re: X server issues and ports
Lets wait for ericbsd opinion too.
Re: X server issues and ports
The current server as 32GB of Ram 2X2TB SATA drive. I found something https://www.soyoustart.com/ca/en/offers/e3-ssd-4.xml. there is a list here, https://www.soyoustart.com/ca/en/essential-servers/.
How mush of space we need to build the whole repository? I have no idea on this.
I have no problem to go with a sever else where It need to run FreeBSD 11.0, more then 16GB of ram and have a possibly a ssd and have good processor.
How mush of space we need to build the whole repository? I have no idea on this.
I have no problem to go with a sever else where It need to run FreeBSD 11.0, more then 16GB of ram and have a possibly a ssd and have good processor.
Re: X server issues and ports
on my own machine, 718 pkgs (many are large pkgs, the average will be a bit lower):
/usr/ports -> 13 GB (that include distfiles and possibly some outdated distfiles accumulated between updates ...)
repository -> 2.3 GB
whole repo: 27.000 pkgs ~= (13 + 2.3) *27.000 / 718 ~= 575 GB (amd64)
add 500 GB for i386 arch.
double it for test and release repository, total is approx. 2 TB
for performance reason at least the swap and ccache should reside on one or two SSD disks.
no need for mirroring here ... the whole thing should be considered as temporary storage. (except the OS itself).
/usr/ports -> 13 GB (that include distfiles and possibly some outdated distfiles accumulated between updates ...)
repository -> 2.3 GB
whole repo: 27.000 pkgs ~= (13 + 2.3) *27.000 / 718 ~= 575 GB (amd64)
add 500 GB for i386 arch.
double it for test and release repository, total is approx. 2 TB
for performance reason at least the swap and ccache should reside on one or two SSD disks.
no need for mirroring here ... the whole thing should be considered as temporary storage. (except the OS itself).
Re: X server issues and ports
I will make a test this night on the server ... to get a more precise approximation.
Re: X server issues and ports
because synth will run several concurrent builders, ideally we may want to distribute the I/O load across as many disks as possible:
- making multiple swap partition, on different disks
- ccache should also reside on a separate SSD disk
- distfiles and repository on another disk
You get the idea.
- making multiple swap partition, on different disks
- ccache should also reside on a separate SSD disk
- distfiles and repository on another disk
You get the idea.
Re: X server issues and ports
to recap, and after that I stop spamming:
ideally:
2 x 300 GB SSD (ccache + swap + /usr/ports + OS
+
2 x 2 TB (repo amd64 + repo i386)
Of course, if that is not possible we will fallback to a lower configuration.
ideally:
2 x 300 GB SSD (ccache + swap + /usr/ports + OS
+
2 x 2 TB (repo amd64 + repo i386)
Of course, if that is not possible we will fallback to a lower configuration.
Re: X server issues and ports
Wow that is a bit more complex that I thought, that server is most likely need to be a custom one for our need.
kraileth any idea on that?
kraileth any idea on that?
Re: X server issues and ports
ericbsd, I wrote "ideally",
as you have seen we can build on the current server at a rate of approx 250 pkgs per hour.
by using separate disks, SSDs, UFS without journaling and other tweaks we can increase the build speed, as I said, we can fallback to what we can achieve.
as you have seen we can build on the current server at a rate of approx 250 pkgs per hour.
by using separate disks, SSDs, UFS without journaling and other tweaks we can increase the build speed, as I said, we can fallback to what we can achieve.
Re: X server issues and ports
I did understand that ASX, I was just saying that to say something, also I did meant to say what kraileth think about that in particular, but more about the whole situation.
Re: X server issues and ports
What about something like this https://www.soyoustart.com/us/offers/e5-sat-2-32.xml?