# ODROID bigLittle only uses 1/3 processing power

**URL:** <https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777>\
**Category:** Product support\
**Created:** [December 20, 2018, 10:16am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777 "2018-12-20T10:16:50Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 10:16am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/1 "2018-12-20T10:16:50Z")

</div>

On an ODROID-XU4 multi-container app, no combination of CPU governing params will allow a specific container to consume more than 50% of CPU.

```
recorder:
    cpu_shares: 820
    cpu_quota: 300000
    build:
      context: ./host-images/recorder
    privileged: true
    cpuset: 0-3
    restart: unless-stopped
    depends_on:
      - "config"
    network_mode: host
    mem_swappiness: 10
    volumes:
      - "resin-data:/data"
```

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 11:29am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/4 "2018-12-20T11:29:51Z")

</div>

With some further testing, even running a single-container setup, CPU is still limited to 50%. 👩‍🦳

---

<div class="post-metadata">

**Author:** ![mikesimos](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mikesimos/32/1418_2.png) [@mikesimos](https://forums.balena.io/u/mikesimos)\
**Post date:** [December 20, 2018, 12:13pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/5 "2018-12-20T12:13:55Z")

</div>

Hi there,  
What is the value of `cpu_shares` for other containers? Some more helpful info may be found [here](https://docs.docker.com/engine/reference/run/#cpu-share-constraint). Have you tried removing/adjusting [`cpu_quota`](https://docs.docker.com/engine/reference/run/#cpu-quota-constraint)?

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 12:46pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/6 "2018-12-20T12:46:35Z")

</div>

I’ve tried both. `cpu_shares` on the other containers is set to `(1024 - 820) / num_containers`.

Could this be a bug related to the XU4’s big.Little ARM architecture? On the host, `/sys/devices/system/cpu/` lists all 8 CPUs, but only 4 will be active at a time. Instead of 4 CPUs, I’m seeing 4 capped at 50% of their potential clock speed.

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 1:02pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/7 "2018-12-20T13:02:47Z")

</div>

Some further testing: using [this cpuset test](https://github.com/balena-io-playground/balena-cpuset), everything performs as expected.

It is only `cpu_quota` and `cpu_shares` that seem to be ignored.

---

<div class="post-metadata">

**Author:** ![zubairlk](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/zubairlk/32/954_2.png) [@zubairlk](https://forums.balena.io/u/zubairlk)\
**Post date:** [December 20, 2018, 2:05pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/8 "2018-12-20T14:05:53Z")

</div>

Seems like you are hitting this issue?

> <https://github.com/moby/moby/issues/26150>

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 2:35pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/9 "2018-12-20T14:35:26Z")

</div>

@zubairlk Good catch. That’s exactly what’s happening. Considering it’s a two year old issue, should I consider it `wontfix`?

---

<div class="post-metadata">

**Author:** ![zubairlk](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/zubairlk/32/954_2.png) [@zubairlk](https://forums.balena.io/u/zubairlk)\
**Post date:** [December 20, 2018, 2:41pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/10 "2018-12-20T14:41:52Z")

</div>

@kazazes  
I can’t say much about where the bug is at the moment thought. kernel or docker.  
Or whether the latest kernel/docker run ok with bigLittle arm cores.

You could try running docker on Odroid - XU4’s default distribution. If it manages to run all cpu cores, then we might be able to patch balenaOS/docker to make it work.

But if that distribution (usually latest stuff as maintained by the device maker) can’t make all CPUs work with docker, we might be in a sticky situation.

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 2:44pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/11 "2018-12-20T14:44:35Z")

</div>

Docker runs fine on the default distribution. This patch seems to be the one.

> <https://github.com/hardkernel/linux/commit/b3ce010128eed16b886b4194cae6e3cca896ba75>

---

<div class="post-metadata">

**Author:** ![mikesimos](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mikesimos/32/1418_2.png) [@mikesimos](https://forums.balena.io/u/mikesimos)\
**Post date:** [December 20, 2018, 3:11pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/12 "2018-12-20T15:11:04Z")

</div>

Hi there,  
We opened an issue for tracking progress on this [here](https://github.com/balena-os/balena-odroid/issues/99)  
Thanks for reporting!  
Cheers

---

<div class="post-metadata">

**Author:** ![zubairlk](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/zubairlk/32/954_2.png) [@zubairlk](https://forums.balena.io/u/zubairlk)\
**Post date:** [December 20, 2018, 3:16pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/13 "2018-12-20T15:16:59Z")

</div>

@kazazes

Can you please share the following for the odroid-xu4 default distribution where you found docker running fine.

`uname -a`  
`cat /etc/os-release`  
`docker info`

Is there a particular reason you think that particular patch is the root cause?

Thanks  
ZubairLK

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 20, 2018, 4:18pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/14 "2018-12-20T16:18:55Z")

</div>

@zubairlk stock ODROID bionic release, docker installed with [get.docker.com script](https://get.docker.com/). No, I have no reason to be sure that that patch is the reason, I just knew it worked on the hardkernel kernel, and started looking through their patches. As you can see there are 8 CPUs available from within docker.

```
root@odroid:~# uname -a
Linux odroid 4.14.85-152 #1 SMP PREEMPT Mon Dec 3 03:00:02 -02 2018 armv7l armv7l armv7l GNU/Linux

root@odroid:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

root@odroid:~# docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 18.09.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
seccomp
  Profile: default
Kernel Version: 4.14.85-152
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: armv7l
CPUs: 8
Total Memory: 1.948GiB
Name: odroid
ID: LNUC:IVMY:B2XH:XHNA:ZOLJ:2SIF:ZRZH:VTKV:EIAW:2VGB:TM5J:RAQR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

root@odroid:~# lscpu
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 2
Vendor ID: ARM
Model: 3
Model name: Cortex-A7
Stepping: r0p3
CPU max MHz: 2000.0000
CPU min MHz: 200.0000
BogoMIPS: 90.00
Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae

root@odroid:~# docker run -it ubuntu /bin/bash
    root@c40b776dfdb3:/# lscpu
    Architecture: armv7l
    Byte Order: Little Endian
    CPU(s): 8
    On-line CPU(s) list: 0-7
    Thread(s) per core: 1
    Core(s) per socket: 4
    Socket(s): 2
    Vendor ID: ARM
    Model: 3
    Model name: Cortex-A7
    Stepping: r0p3
    CPU max MHz: 2000.0000
    CPU min MHz: 200.0000
    BogoMIPS: 90.00
    Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae
```

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 24, 2018, 4:31pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/16 "2018-12-24T16:31:50Z")

</div>

I’ve tested [akuster/meta-odroid@sumo…thud](https://github.com/akuster/meta-odroid/compare/sumo...thud) and can confirm that the fix lies somewhere in there. Considering the bug doesn’t exist on [@hardkernel](https://github.com/hardkernel)’s even older images, the regression seems to have been introduced in `meta-odroid:sumo` (which was being built off of hardkernel until `thud` , I believe).

[`meta-odroid:thud` is compatible with `sumo`](https://github.com/akuster/meta-odroid/blob/f43a28ca491c7fd560173c6a8616c50d246488c7/conf/layer.conf#L14), but can’t be pulled into this repo until there is some patch re-work. There are some compile-time problems with both layers trying to write the boot image, and `meta-balena` 's config checks are throwing warnings because of the kernel bump. I will get to this after Christmas, but would love some help.

[@balena-os](https://github.com/balena-os), what is the timeline on [balena-os/meta-balena#1313](https://github.com/balena-os/meta-balena/issues/1313)? `thud` compatibility on the `meta-balena-*` side would do away with this instantly.

`meta-odroid` is flying ahead with 4.19 LTS support with just one dev. I have been so impressed with balena to-date on the tooling end, but in the middle of a time-critical development cycle this is really crushing us, we’ve committed to this stack happily, but I’m now sensing that balena is focused on listing as much semi-functional board compatibility as possible rather than getting true support for a subset of boards beyond Pis. I’m only realizing now that I can’t find any test cases for balena kernel images.

This may be a very simple fix, I don’t mean to come off as condescending or unappreciative, but we’ve committed months to this platform for a large scale production run and I really hope a critical malfunction of one of your more powerful supported boards would be a priority. This issue seems to have gone unnoticed through the entire development of this image. The above referenced [moby/moby#26150](https://github.com/moby/moby/issues/26150) is two years old. Surely someone would have noticed that this board was running at a third of its processing power if there was any hardware QA happening? There are a year’s worth of one-line-fix issues in `meta-resin-odroid`. I’m sorry to be blunt, but these are the questions I have to ask myself as I’m evaluating balena for a 1k+ node deployment.

The product in question is extremely dependent on consistent functionality of the underlying OS, and as Linus would say, there are no userspace bugs.

I fell in love with balena. I will stick with it. I’ll switch our entire architecture to another supported board if I have to, redesign our enclosures, thermal management, etc., we pivoted our entire stack when we realized how good of a fit this would be. I just want to voice my concern that this issue has existed for so long, unnoticed, and that there is no published LTS plan (see [trello](https://trello.com/b/9CSzdCXQ/balena-product-roadmap), the roadmap is completely out of sync with product release by \>6 months in some instances), and your minimum SLA is $16k/year. Where is the focus? Hobbyist boards or a revolutionary IaaS provider?

If balenaCloud and OS are beta products, please, please advertise them as such. [People](https://forums.balena.io/t/regular-crashes/4501/29) (myself included) are [building](https://forums.balena.io/t/latest-resinos-prevents-wifi-access-on-rpi/3579/25) products, and eventually businesses on the [assumption](https://forums.balena.io/t/container-in-endless-installing-starting-installing-stopping-loop-since-upgrade-from-resin-os-2-15-1-rev2-to-balenaos-2-27-0-rev1/4790) that [this](https://forums.balena.io/t/device-is-offline-all-the-time/3101/12) will scale with them. There seems to be a lot of flux and not a lot of direction.

---

<div class="post-metadata">

**Author:** ![shaunmulligan](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/shaunmulligan/32/34_2.png) [@shaunmulligan](https://forums.balena.io/u/shaunmulligan)\
**Post date:** [December 26, 2018, 4:52pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/17 "2018-12-26T16:52:16Z")

</div>

Hi @kazazes, I would like to first apologise for the inconvenience this bug has caused and thank you for highlighting it. We always try our best to cover as much of the supported hardware on boards as possible and unfortunately have to rely heavily on the BSP layers for that. In most cases we use or make a BSP, ideally official, and our tests pass. The QA tests themselves guarantees a minimal standard of functionality, not that we push the board to its limits, at least not without community assistance.

The XU4 board has historically had been added when we rapidly expanded the number of boards supported and it was hoped that it would gain a lot of traction, but to this day, there are less than 50 in use on the platform which means that bugs like this can unfortunately go unnoticed for a long time, where as it this bug had been on the RPI3, Intel NUC or TX2 it would have been caught by the community very early on.

All that being said, we have seen a marked improvement in the XU4 support both from hardkernel itself and the BSP layer and I think this board will start to get greater usage. I have asked the OS team for a timeline on thud support, it shouldn’t be too far off. When I have a more firm time frame I will come back and add it here.

On balenaCloud and the OS, these are definitely not beta products and the have hundreds on companies deploy thousands of devices each and relying on us completely as the backbone for their infrastructure. Some of more serious and niche customers even rely on us to build and support their custom hardware or device type in which we work with them to ensure their boards have the exact hardware functionality they need for their usecase. We are in the process of defining our support release versions of the OS, so keep an eye out for that early next year 🙂

We really value your feedback and everyone in the community. We are working our hardest to try provide a platform that is both rock solid and constantly improving. In 2019 we hope to launch a number of things to improve stability and visibility across that stack, its gonna be a great year for Balena.

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [December 28, 2018, 3:08pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/18 "2018-12-28T15:08:43Z")

</div>

@shaunmulligan, thank you for such a thorough response. I had no idea there were so few on the platform, I’d figured there were way more! I understand that you can’t run hardware tests on all of the boards, so that makes sense.

I look forward to moving forward with the platform as we move forward with a commercial release; we’ve switched to an armbian build in the interim. Please let me know when you have that timeframe.

Peter

---

<div class="post-metadata">

**Author:** ![shaunmulligan](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/shaunmulligan/32/34_2.png) [@shaunmulligan](https://forums.balena.io/u/shaunmulligan)\
**Post date:** [January 10, 2019, 10:17am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/19 "2019-01-10T10:17:59Z")

</div>

Hey @kazazes, just and update on this, Thud support is under way here: [https://github.com/balena-os/meta-balena/pull/1351](https://github.com/balena-os/meta-balena/pull/1351) , the only one worry here is the "balena-engine needs support for the go version provided by thud (1.11.1) " part, as docker/balena-engine is particularly sensitive to updates in go version, so we need to treat that with care and test thoroughly. Other than that, things seem to be progressing well and hopefully we can have thud out soon.

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [February 13, 2019, 1:38am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/20 "2019-02-13T01:38:02Z")

</div>

Any update here?

---

<div class="post-metadata">

**Author:** ![thgreasi](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/thgreasi/32/454_2.png) [@thgreasi](https://forums.balena.io/u/thgreasi)\
**Post date:** [February 15, 2019, 9:49am UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/21 "2019-02-15T09:49:05Z")

</div>

Hi @kazazes,  
The PR is still in progress of finalizing.  
We will get back to you once this gets released.

---

<div class="post-metadata">

**Author:** ![kazazes](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/kazazes/32/1432_2.png) [@kazazes](https://forums.balena.io/u/kazazes)\
**Post date:** [February 25, 2019, 3:46pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/22 "2019-02-25T15:46:50Z")

</div>

@thgreasi could you please provide a link to the PR’s fork for testing? Can’t seem to find it on GitHub.

---

<div class="post-metadata">

**Author:** ![thgreasi](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/thgreasi/32/454_2.png) [@thgreasi](https://forums.balena.io/u/thgreasi)\
**Post date:** [February 26, 2019, 12:10pm UTC](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777/23 "2019-02-26T12:10:08Z")

</div>

@kazazes the branch for the [above PR](https://github.com/balena-os/meta-balena/pull/1351) should be [https://github.com/balena-os/meta-balena/tree/ag/thud-support](https://github.com/balena-os/meta-balena/tree/ag/thud-support) .

[Next page](https://forums.balena.io/t/odroid-biglittle-only-uses-1-3-processing-power/4777.md?page=2)
