You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
docker run ... quay.io/influxdb/influxdb:2.0.0-beta
docker exec -it influxdbv2 bash
time influx version
Expected behavior:
That trivial actions are quickly performed
Actual behavior:
Every command, even a trivial one, takes 2s CPU time
time influx version
Influx CLI 2.0.0-beta.12 (git: ff620782eb) build_date: 2020-06-21T10:17:39Z
real 0m2.113s
user 0m2.134s
sys 0m0.016s
I extracted the influx program with docker cp and executed it one the same host but outside of the docker container. This gives slightly faster execution times, but still values around 1.6s:
time ./influx version
Influx CLI 2.0.0-beta.12 (git: ff620782eb) build_date: 2020-06-21T10:21:30Z
real 0m1.639s user 0m1.671s sys 0m0.004s
Environment info:
System info: Run uname -srm: Linux 5.3.0-51-generic x86_64
InfluxDB version: Run influxd version: Influx CLI 2.0.0-beta.12 (git: ff62078)
Other relevant environment details: Container runtime: docker
/proc/cpuinfo: Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
docker run ... quay.io/influxdb/influxdb:2.0.0-beta
docker exec -it influxdbv2 bash
time influx version
Expected behavior:
That trivial actions are quickly performed
Actual behavior:
Every command, even a trivial one, takes 2s CPU time
I extracted the
influx
program withdocker cp
and executed it one the same host but outside of the docker container. This gives slightly faster execution times, but still values around 1.6s:Environment info:
uname -srm
: Linux 5.3.0-51-generic x86_64influxd version
: Influx CLI 2.0.0-beta.12 (git: ff62078)/proc/cpuinfo
: Intel(R) Core(TM) i3-8109U CPU @ 3.00GHzThe text was updated successfully, but these errors were encountered: