I have a lot of page faults when using Sugar SAT based solver
I am using Sugar v2-3-3 (an SAT-based Constraint Solver) with minisat solver2.2.0 to run an experiment, I run my experiment on Kernel Linux server with 16GB RAM and 4 VCPU and I am using Java version 10 (Java Max Heap size is 12 GB and Min size is 8GB).
The experiment is based on running 5 different sugar files 400 time and extracts the average CPU, memory and time (using the command /usr/bin/time) for running each file. However, when scrolling the output of the time command I noticed that there is a lot of page faults, leading to irrational results, where the CPU percent for some of the large files is lower than smaller ones. The maximum file I have is 100MB.
Can anyone help me to explain why I am having page fault although I have big enough memory, and how to avoid page fault?
The results are as follows:
⦁ 50.27% 00:05.03 211303.68
⦁ 43.22% 00:15.03 480789.36
⦁ 43.19% 00:21.25 577915.12
⦁ 40.86% 00:26.07 717707.88
⦁ 41.22% 00:30.49 853791.88
linux memory java
edited Feb 12 at 3:08
JakeGould
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
add a comment |
I am using Sugar v2-3-3 (an SAT-based Constraint Solver) with minisat solver2.2.0 to run an experiment, I run my experiment on Kernel Linux server with 16GB RAM and 4 VCPU and I am using Java version 10 (Java Max Heap size is 12 GB and Min size is 8GB).
The experiment is based on running 5 different sugar files 400 time and extracts the average CPU, memory and time (using the command /usr/bin/time) for running each file. However, when scrolling the output of the time command I noticed that there is a lot of page faults, leading to irrational results, where the CPU percent for some of the large files is lower than smaller ones. The maximum file I have is 100MB.
Can anyone help me to explain why I am having page fault although I have big enough memory, and how to avoid page fault?
The results are as follows:
⦁ 50.27% 00:05.03 211303.68
⦁ 43.22% 00:15.03 480789.36
⦁ 43.19% 00:21.25 577915.12
⦁ 40.86% 00:26.07 717707.88
⦁ 41.22% 00:30.49 853791.88
linux memory java
edited Feb 12 at 3:08
JakeGould
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
add a comment |
I am using Sugar v2-3-3 (an SAT-based Constraint Solver) with minisat solver2.2.0 to run an experiment, I run my experiment on Kernel Linux server with 16GB RAM and 4 VCPU and I am using Java version 10 (Java Max Heap size is 12 GB and Min size is 8GB).
The experiment is based on running 5 different sugar files 400 time and extracts the average CPU, memory and time (using the command /usr/bin/time) for running each file. However, when scrolling the output of the time command I noticed that there is a lot of page faults, leading to irrational results, where the CPU percent for some of the large files is lower than smaller ones. The maximum file I have is 100MB.
Can anyone help me to explain why I am having page fault although I have big enough memory, and how to avoid page fault?
The results are as follows:
⦁ 50.27% 00:05.03 211303.68
⦁ 43.22% 00:15.03 480789.36
⦁ 43.19% 00:21.25 577915.12
⦁ 40.86% 00:26.07 717707.88
⦁ 41.22% 00:30.49 853791.88
linux memory java
edited Feb 12 at 3:08
JakeGould
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
I am using Sugar v2-3-3 (an SAT-based Constraint Solver) with minisat solver2.2.0 to run an experiment, I run my experiment on Kernel Linux server with 16GB RAM and 4 VCPU and I am using Java version 10 (Java Max Heap size is 12 GB and Min size is 8GB).
The experiment is based on running 5 different sugar files 400 time and extracts the average CPU, memory and time (using the command /usr/bin/time) for running each file. However, when scrolling the output of the time command I noticed that there is a lot of page faults, leading to irrational results, where the CPU percent for some of the large files is lower than smaller ones. The maximum file I have is 100MB.
Can anyone help me to explain why I am having page fault although I have big enough memory, and how to avoid page fault?
The results are as follows:
⦁ 50.27% 00:05.03 211303.68
⦁ 43.22% 00:15.03 480789.36
⦁ 43.19% 00:21.25 577915.12
⦁ 40.86% 00:26.07 717707.88
⦁ 41.22% 00:30.49 853791.88
linux memory java
linux memory java
edited Feb 12 at 3:08
JakeGould
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
edited Feb 12 at 3:08
JakeGould
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
edited Feb 12 at 3:08
JakeGould
32k1098140
edited Feb 12 at 3:08
JakeGould
32k1098140
edited Feb 12 at 3:08
JakeGould
32k1098140
32k1098140
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
asked Feb 12 at 2:52
Alaa OqailyAlaa Oqaily
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404673%2fi-have-a-lot-of-page-faults-when-using-sugar-sat-based-solver%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404673%2fi-have-a-lot-of-page-faults-when-using-sugar-sat-based-solver%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
