You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2023/12/20 11:44:11 UTC
[PR] fix(e2e): quarkus native is memory eager [camel-k]
squakez opened a new pull request, #4999:
URL: https://github.com/apache/camel-k/pull/4999
In the latest releases it seems it requires at least 30% more in memory usage.
Hopefully this PR solves the problem we are seeing in Quarkus native checks by setting a higher amount of resources and no ceiling to the memory to use.
Closes #4723
<!-- Description -->
<!--
Enter your extended release note in the below block. If the PR requires
additional action from users switching to the new release, include the string
"action required". If no release note is required, write "NONE".
You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure
the text is added to the right section of the release notes.
-->
**Release Note**
```release-note
fix(e2e): quarkus native is memory eager
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(e2e): quarkus native is memory eager [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on PR #4999:
URL: https://github.com/apache/camel-k/pull/4999#issuecomment-1864550586
> I can't help but wonder if we should we be concerned by that increase of memory usage...
We should, but probably we cannot do much more than trying to increase vertical scaling. I guess it's a problem of all Quarkus applications.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(e2e): quarkus native is memory eager [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on PR #4999:
URL: https://github.com/apache/camel-k/pull/4999#issuecomment-1866617214
Somthething strange is happening with the error
```
The push refers to repository [kind-registry:5000/apache/camel-k]
Get "https://kind-registry:5000/v2/": dial tcp: lookup kind-registry on 127.0.0.53:53: server misbehaving
make: *** [image-push] Error 1
```
I'm closing this PR and try a new one :/
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(e2e): quarkus native is memory eager [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed pull request #4999: fix(e2e): quarkus native is memory eager
URL: https://github.com/apache/camel-k/pull/4999
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(e2e): quarkus native is memory eager [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed pull request #4999: fix(e2e): quarkus native is memory eager
URL: https://github.com/apache/camel-k/pull/4999
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org