| 1 |
On 13/07/2016 21:13, James wrote: |
| 2 |
> Jeremi Piotrowski <jeremi.piotrowski <at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>>>> Has anyone attempted to install a self hosted gitlab on gentoo server(s)? |
| 6 |
> |
| 7 |
> |
| 8 |
>> I would deploy it with docker. The gitlab guys push official images of the |
| 9 |
>> main gitlab app[1] and CI runners[2] to dockerhub. That should be |
| 10 |
>> the easiest path to getting it up and running in no time. |
| 11 |
> |
| 12 |
> Docker runs everywhere, including Mesos clusters. |
| 13 |
> |
| 14 |
>> That being said, gitlab does not really play well with clustering in |
| 15 |
>> general. I don't think the main part of the app does any kind of |
| 16 |
>> horizontal scaling (gitlab.com is hosted on a single server) so you need a |
| 17 |
>> fairly beefy server. |
| 18 |
> |
| 19 |
> That's weird. Almost every type of heavy load is finding it's way to |
| 20 |
> clusters now; many via containers some on bare metal clusters. Granted, very |
| 21 |
> often a custom, scheduler/framework has to be modified or custom developed, |
| 22 |
> but I find it hard to believe there is no way to massively speed up |
| 23 |
> something like gitlab on a robust linux cluster. That dragon has been |
| 24 |
> sleighed for most all load problems, be it HPC, networking issues, or |
| 25 |
> security audits, etc etc. Often, a cloud/cluster software can be radically |
| 26 |
> sped up by allocating lots of extra ram to the framework it is running on. |
| 27 |
> Cloud vendors charge way to much for extra ram, so performance of |
| 28 |
> ram-intensive services are often run where there is ample ram. |
| 29 |
|
| 30 |
Depends. It might all be running on a single-threaded ruby process in |
| 31 |
the middleware :-) |
| 32 |
|
| 33 |
Don't laugh, I've seen stranger things. |
| 34 |
|
| 35 |
Alan |
Archives