Table of contents
Problem Description:
When students play gitlab, they report an error through web page access:
Whoops, GitLab is taking too much time to respond
Solution
Just wait. . . . .
problem causes
Let's analyze the reasons:
1. gitlab is a huge project that consumes a lot of memory, and it takes a long time to start and load.
2. When we report an error in gitlab, we can dynamically observe the memory usage of the server.
[root@localhost ~]# free -mh[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 2.9G 3.1G 143M 1.6G 4.3G
Swap: 2.0G 0B 2.0G
------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.5G 2.5G 145M 1.7G 3.7G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.6G 2.4G 145M 1.7G 3.6G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.6G 2.3G 145M 1.7G 3.6G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.6G 2.3G 145M 1.7G 3.6G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.6G 2.3G 145M 1.7G 3.6G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.7G 2.3G 145M 1.7G 3.5G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 3.7G 2.3G 145M 1.7G 3.5G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 4.0G 2.0G 146M 1.7G 3.2G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 4.0G 2.0G 147M 1.7G 3.2G
Swap: 2.0G 0B 2.0G
-------------
[root@localhost ~]# free -mh
total used free shared buff/cache available
Mem: 7.6G 4.0G 2.0G 147M 1.7G 3.2G
Swap: 2.0G 0B 2.0GWhen observing the usage of free memory, we found that during this period of time, the free memory has been decreasing.
It means that there is a program that has been loading and using memory.
Of course this is exactly the startup process of gitlab.
After the startup is complete, the amount of free memory no longer decreases. It means that the startup of gitlab is completed, we visit at this time, it is normal
