The only issue is the volume of data hides potential problems. For example 
I'm in the process of migrating to a 
new server because Gitlab is very slow, but monitoring was showing 100ms 
average latency. 

With a little digging i managed to see that most user requests are in the 
500ms range with a few taking multiple seconds. 

The same is true for the database, i tried to track down why a 1.5GB db was 
using over 3GB of RAM. Turns out 
most time is spent reading `ci_builds` table: 

<https://lh3.googleusercontent.com/-6SMn8seChJM/WMFX2m6jbzI/AAAAAAAANJA/Ejpv7fdZenIq0NBHHYkI60vLSKxTfdndwCLcB/s1600/Selection_007.png>


It might not cause problems, but it makes it hard to notice the real ones 
:) 


On Wednesday, March 8, 2017 at 6:17:21 PM UTC+2, Aleksey Tsalolikhin wrote:

> Great, glad you figured it out. 
>
> I don't have any data for your 2nd question now. I'll let somebody else 
> answer that.
>
> I do know the runners check in with the coordinator constantly. That's 
> part of the architecture. Is it causing any issue?
>
> On Mar 8, 2017 11:07 AM, "Alexandru Keszeg" <[email protected] 
> <javascript:>> wrote:
>
> I ended up grepping the logs for builds/register to get the IP's. 
>
> What do you think about my other question, is it normal to have 100 000 
> requests over a few days from gitlab ci runners?
>
>
> On Wednesday, March 8, 2017 at 3:40:43 PM UTC+2, Aleksey Tsalolikhin wrote:
>
>> I've never seen the runner IP addresses in the interface...  but if you 
>> run "sudo gitlab-runner list" on your runner hosts, you will get the link 
>> of the runners on each host along with the token of each runner.   Hope 
>> this helps.
>> ᐧ
>>
>> -- 
>> Need training on CFEngine, Git or Time Management?  Email 
>> [email protected].
>>
>> On Wed, Mar 8, 2017 at 2:41 AM, Alexandru Keszeg <[email protected]> 
>> wrote:
>>
>>> Hello, 
>>>
>>> I'm managing a gitlab instance with about 9 gitlab ci runners configured.
>>>
>>> `v1: /builds/register(POST)` is the highest throughput request at 182 
>>> rpm and 22% total time consumed on the server.
>>>
>>> Here is an image with the top transactions, and as you can see, the 
>>> usual traffic is barely noticeable from all the gitlab ci registrations.
>>>
>>>
>>> <https://lh3.googleusercontent.com/-LFm8y9y5GpM/WL_H6drHvVI/AAAAAAAANIk/liD4AwOAnksrhSv1hIpmTHfaKkEH2_v8wCLcB/s1600/Selection_007.png>
>>>
>>> Questions? 
>>>
>>> 1, is this level of traffic from 9 gitlab ci runners normal? 
>>> 2, is there a place in the interface where i can see the IP's for the 
>>> runners? The admin only shows me a token, not the actual IP.  
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "GitLab" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/gitlabhq/9a763406-6ccd-43d9-b6ba-906c8b219138%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/gitlabhq/9a763406-6ccd-43d9-b6ba-906c8b219138%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/gitlabhq/75ad100d-e7f0-47e7-9c57-ca38120a81aa%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/gitlabhq/75ad100d-e7f0-47e7-9c57-ca38120a81aa%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/a68ce61a-22c2-4a56-9d1a-638a8884e35e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to