When using docker container deployment services for testing, only one core can be invoked, resulting in lower testing speed.

[openspeedtest]

When using docker container deployment services for testing, only one core can be invoked, resulting in lower testing speed.

[openspeedtest]

@qianxu2001
Which device?
I tested this on a Raspberry Pi Model B and got 940+ on both sides.
Did you use the Official Docker image?
If this is an Old Raspberry Pi Model B, you may need to OverClock it to achieve full speed.
We are using Nginx Server. It should use all cores, but Single Core performance is Very Important.
All NGINX Performance Tuning tips can be used or tested.
When I tested my Raspberry Pi Model B last time, Core 1 was utilised on average 60 to 70%. That is not unusual.

400+Gb.Data.Transfer.in.1.Hour.Network.Stress.Test.Continuous.Speed.Test.Raspberry.Pi.4B.8.GB.RAM.mp4

[qianxuu]

My device is powered by an Amlogic S805 processor, which I cannot overclock, and I am trying Nginx performance tuning.
I am using the official Docker image and just tried to modify /etc/nginx/nginx.conf inside the container, but vi prompts that 'nginx.conf' is read only.

[openspeedtest]

@qianxu2001 Here is the Docker Image Project Build and Test using local image.

[qianxuu]

@qianxu2001 Here is the Docker Image Project Build and Test using local image.

I modified the configuration, using about 1.3 cores, the test speed is close to 800Mbps, the effect is not obvious, I will replace the device to deploy the service in the near future, thank you for your answer.

[openspeedtest]

If you find the modified configuration useful for everyone, let me know. We can modify the docker image.
Thank you. @qianxu2001