<blockquote>
  <p>It seems that my cluster is capped at 3% of maximum utilization, if I
  read the units correctly. This makes no sense at all, why isn't it
  capable of reaching 100% ?</p>
</blockquote>

<p>Why do you think it does make no sense at all? </p>

<blockquote>
  <p>I ran a few tests that created quite a few pods</p>
</blockquote>

<p>What is a few tests?</p>

<blockquote>
  <p>(each pod running basically an hello world script)</p>
</blockquote>

<p>What does this script do? Print helloworld? If that is the case then it could be possible that the cluster will not use 100%.</p>

<p>By the way, how large is the cluster? How many agents? How many memory? So if the cluster possesses 1024GB of memory then it could be the case it is using 3%.</p>

<p>In summary, to indicate whether <code>something makes no sense at all</code> a number of facts is required:</p>

<ul>
<li>content of the helloworld script</li>
<li>characteristics of the cluster, e.g. totol cpu, memory, type of disks, storage capacity, number of agents, masters</li>
<li>definition of <code>few tests</code> and <code>few pods</code>. How many tests were run, frequency, e.g. 10/s, how many pods</li>
</ul>

<p>If you would really like to loadtest a k8s cluster, kubernetes has some documentation about this, e.g. <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/" rel="nofollow noreferrer">this document</a> explains how to load test a k8s cluster and in this case force autoscaling.</p>

CC BY-SA 3.0
2017-12-26T11:12:19.847Z
thank you for the answer, I realize now my question needs a lot of clarification. Let me edit.
Overdrivr
CC BY-SA 3.0
2017-12-26T11:10:51.930Z
2017-12-26T11:28:11.477Z
2017-12-26T11:28:11.477Z
030
<p>I have a 3-node kubernetes cluster with 3 <code>n1-standard-1 :1 vCPU, 3,75 Go RAM</code>, in a gcloud projet. Recently, I ran a test that created quite a few jobs (about 150). Half the jobs were running an hello world script, the other half were failing due to configuration error, and those jobs kept retrying by restarting new pods.</p>

<p>In my console I observed the following graph:</p>

<p><a href="https://i.sstatic.net/HAAvj.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/HAAvj.png" alt="is the unit % or 1.0"></a></p>

<p>It seems that my cluster is capped at 3% of maximum utilization, if I read the units correctly. What bothers me is that in my test, the amount of pods/utilisation should not be constant, so I was not expecting the utilization to be a flat line like this.</p>

<p>Also, I noticed about about 30 pods were in unschedulable state, so my initial thought was that I reached maximum utilization of the instance. </p>

<h1>EDIT</h1>

<p>It is clear now that my test is too poorly designed, so I cannot conclude about maximum utilization so far.</p>

CC BY-SA 3.0
2017-12-26T11:20:03.420Z
Could you add the content of the script?
030
CC BY-SA 3.0
2017-12-26T11:21:07.553Z
`30 pods were in unschedulable state` Could you add the output of `kubectl get services`?
030
<kubernetes><google-cloud-platform>
Meaning of metrics in Google Cloud Console
Overdrivr
# Meaning of metrics in Google Cloud Console

(Asked by: username_0 on 2017-12-26)

I have a 3-node kubernetes cluster with 3 `n1-standard-1 :1 vCPU, 3,75 Go RAM`, in a gcloud projet. Recently, I ran a test that created quite a few jobs (about 150). Half the jobs were running an hello world script, the other half were failing due to configuration error, and those jobs kept retrying by restarting new pods.

In my console I observed the following graph:

[![is the unit % or 1.0](https://i.sstatic.net/HAAvj.png)](https://i.sstatic.net/HAAvj.png)

It seems that my cluster is capped at 3% of maximum utilization, if I read the units correctly. What bothers me is that in my test, the amount of pods/utilisation should not be constant, so I was not expecting the utilization to be a flat line like this.

Also, I noticed about about 30 pods were in unschedulable state, so my initial thought was that I reached maximum utilization of the instance.

# EDIT

It is clear now that my test is too poorly designed, so I cannot conclude about maximum utilization so far.

**Tags:** kubernetes, google-cloud-platform

> **Comments:**
> **username_1**: Could you add the content of the script?  
> **username_1**: `30 pods were in unschedulable state` Could you add the output of `kubectl get services`?  

---

## 1 answers

### Answer by username_1 on 2017-12-26. Score: 4 | Accepted answer

> It seems that my cluster is capped at 3% of maximum utilization, if I
> read the units correctly. This makes no sense at all, why isn't it
> capable of reaching 100% ?

Why do you think it does make no sense at all?

> I ran a few tests that created quite a few pods

What is a few tests?

> (each pod running basically an hello world script)

What does this script do? Print helloworld? If that is the case then it could be possible that the cluster will not use 100%.

By the way, how large is the cluster? How many agents? How many memory? So if the cluster possesses 1024GB of memory then it could be the case it is using 3%.

In summary, to indicate whether `something makes no sense at all` a number of facts is required:

* content of the helloworld script
* characteristics of the cluster, e.g. totol cpu, memory, type of disks, storage capacity, number of agents, masters
* definition of `few tests` and `few pods`. How many tests were run, frequency, e.g. 10/s, how many pods

If you would really like to loadtest a k8s cluster, kubernetes has some documentation about this, e.g. [this document](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) explains how to load test a k8s cluster and in this case force autoscaling.

> **Comments:**
> **username_0**: thank you for the answer, I realize now my question needs a lot of clarification. Let me edit.  

---

