Check whether it is possible to reduce the amount of RAM spent by the AS2 itest #1672 #1686
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JiriOndrusek
force-pushed
the
1672_as2-too-much-time
branch
2 times, most recently
from
f289035
to
f7a799e
Compare
JiriOndrusek
force-pushed
the
1672_as2-too-much-time
branch
from
f7a799e
to
4345578
Compare
JiriOndrusek
changed the title
JiriOndrusek
force-pushed
the
1672_as2-too-much-time
branch
from
4345578
to
edc69d3
Compare
|
@ppalaga The current build time is 7 mins faster then before
(unfortunately I've missed one I'll try to find another optimization, but IMHO result form the current build is much better then I hoped for. |
That's great! I'd like to clear some questions on Monday, switching to draft till then. |
jamesnetherton
force-pushed
the
camel-master
branch
from
c46d142
to
ccab6f2
Compare
JiriOndrusek
force-pushed
the
1672_as2-too-much-time
branch
from
edc69d3
to
16390b3
Compare
|
Replaced by #1723 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1672
Adds configuration for bouncycastle extension. It now requires user to define all ciphers and digest at build time, which has impact on memory requirements.
This change can be merged. It is an isolated fix.
I'll continue with the investigation in case that there is another way of reducing requirements of as2 integration test module.
[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html