In part 1 of our 'Understanding your graphs' mini-series, we talked about GitHub Enterprise System Health graphs. We'll now look at GitHub Enterprise Processes graphs.
The processes graph section looks deeper into the major individual services which make up the GitHub Enterprise appliance. Looking at these services individually can show how usage trends impact system resources over time.
longpollprocess will often have the highest average, with more peaks and valleys reflecting daily web UI usage trends.
resqueprocess groups normally consume the highest amount of memory, followed by
git-daemonprocesses are most influenced by user activity.
unicornprocess normally consumes the most CPU time.
unicornconsumes the most CPU time, followed by
babeldread Input/Output Oerations Per Scond (IOPS) values are influenced by Git fetch / pull activity.
unicornread IOPS are influenced by web application or API
resqueread IOPS are from background jobs, such as regular repository maintenance and repacking.
git-daemonwrite IOPS reflect Git push activity and is most often the largest consumer of write IOPS.
resquebackground jobs, such as search indexing, and repository repacking are also be a large consumer of write IOPS
POSToperations are often the largest influencers of this graph.
There's more to come in the "Understanding your graphs" mini-series. If you'd like to follow along, subscribe to the "Understanding your graphs" label. Please let us know if you have any questions in the comments!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.