-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Add performance testing #63
Conversation
That's because stdout is empty:
Here is the output of the build:
How do the build here differ from the previous one we are doing? |
The docker build --no-cache didn't change a thing |
# (the container would be gone then) | ||
host.run( | ||
f"{container_runtime.runner_binary} stop " | ||
+ container_runtime.get_image_id_from_stdout(cmd.stdout) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does that work properly ? See also L56. (Or maybe build and run don't have the same kind of output?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears to do the right thing on my machine: no containers are left on the system with both podman and docker after running the performance tests.
Rebased, squashed a few commits together. |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be closer to the reality between UBI and BCI, we need to also have a base container built, or need to build both base containers in this test.
0469dc9
to
a75bda2
Compare
This is still a draft... More work needs to be done to compare the different containers:
|
Without this, we are not comparing our BCI to UBI. This is a problem, as we are not proving the value of our efforts, from a technical standpoint. We should show why our containers are probably better from a technical perspective (or show where we can improve). This fixes it by adding multiple builds of of the same application, in 3 different runtimes: BCI, SLE current default image, and UBI from RH. To make it significant, I chose to use software which makes sense for ISVs or SUSE Hub, so I chose Kafka. The Kafka UBI files come from confluentinc/kafka-images/kafka. The Dockerfile has been renamed, and follow up changes will need to be tracked in git, so we can easily compare them.
Without this, we are reusing the default env. This is a problem, as it does extra stuff we don't need, like fetching containers. To represent a user behaviour, no prefetch should be done.
stdlib, external, then internal libs.
This will make sure the latest containers are built. It will remove a few transient issues.
Closing this for now. Please don't hesitate to reopen if there is time to rebase and finish it off! |
Without this, we are not comparing our BCI to UBI.
This is a problem, as we are not proving the value of our
efforts, from a technical standpoint.
We should show why our containers are probably better from
a technical perspective (or show where we can improve).
This fixes it by adding multiple builds of of the same
application, in 3 different runtimes: BCI, SLE current default
image, and UBI from RH. To make it significant, I chose
to use software which makes sense for ISVs or SUSE
Hub, so I chose grafana.
The grafana UBI files come from RH dockerfile in https://catalog.redhat.com/software/containers/rhel8/grafana/5edf9c35dd19c7063a62aff6?container-tabs=dockerfile
Closes: #41