Mixing
A way/ tool to make an estimation of execution time for an APP/ task
I'am trying to run real-life experiment for an application in Raspberry Pi, and I need to estimate or predicate the execution time for the application. in other words, before execution/ run the task i need to know how long (roughly) this task/app going to take to get the result back. I have identified several techniques and works that have been done before. but most of it are simulation work which doesn't work with real-life experiment. does anyone can help me with any idea or technique (No code). thank you in advance
prediction execution-time estimation
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
add a comment |
I'am trying to run real-life experiment for an application in Raspberry Pi, and I need to estimate or predicate the execution time for the application. in other words, before execution/ run the task i need to know how long (roughly) this task/app going to take to get the result back. I have identified several techniques and works that have been done before. but most of it are simulation work which doesn't work with real-life experiment. does anyone can help me with any idea or technique (No code). thank you in advance
prediction execution-time estimation
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
add a comment |
I'am trying to run real-life experiment for an application in Raspberry Pi, and I need to estimate or predicate the execution time for the application. in other words, before execution/ run the task i need to know how long (roughly) this task/app going to take to get the result back. I have identified several techniques and works that have been done before. but most of it are simulation work which doesn't work with real-life experiment. does anyone can help me with any idea or technique (No code). thank you in advance
prediction execution-time estimation
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
I'am trying to run real-life experiment for an application in Raspberry Pi, and I need to estimate or predicate the execution time for the application. in other words, before execution/ run the task i need to know how long (roughly) this task/app going to take to get the result back. I have identified several techniques and works that have been done before. but most of it are simulation work which doesn't work with real-life experiment. does anyone can help me with any idea or technique (No code). thank you in advance
prediction execution-time estimation
prediction execution-time estimation
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
edited Jan 2 at 15:14
Ali Jaddoa
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
asked Jan 2 at 14:55
Ali JaddoaAli Jaddoa
12
12
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Estimating the execution time of an application or function is going to be difficult in any context. You might want to look up the halting problem for some insight to why. It's impossible to determine whether a given program will finish executing, and therefore, you can't really tell how long a given program will take to finish executing.
For general computing, varying hardware capabilities of any given system will always have an effect on the execution time of a program. Raspberry Pi is a little more discrete than that, and therefore more predictable in that sense, but those specifications will not always be consistent across its various versions. That adds to the complexity of determining a run time.
Practically, the most reliable way to determine how long a process will take would be to just run it and time it. If you absolutely need predicted times for something, you might be able to do a bit of a composite estimate - time the smaller chunks of the application separately, and then use those to determine how long you expect the application as a whole to run. For most situations, though, it would be much faster to just run the program itself rather than trying to predict it.
answered Jan 2 at 16:01
movip1991movip1991
865
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
add a comment |
Store the time before and after the execution ? Then you could know the execution time
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f54008487%2fa-way-tool-to-make-an-estimation-of-execution-time-for-an-app-task%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Estimating the execution time of an application or function is going to be difficult in any context. You might want to look up the halting problem for some insight to why. It's impossible to determine whether a given program will finish executing, and therefore, you can't really tell how long a given program will take to finish executing.
For general computing, varying hardware capabilities of any given system will always have an effect on the execution time of a program. Raspberry Pi is a little more discrete than that, and therefore more predictable in that sense, but those specifications will not always be consistent across its various versions. That adds to the complexity of determining a run time.
Practically, the most reliable way to determine how long a process will take would be to just run it and time it. If you absolutely need predicted times for something, you might be able to do a bit of a composite estimate - time the smaller chunks of the application separately, and then use those to determine how long you expect the application as a whole to run. For most situations, though, it would be much faster to just run the program itself rather than trying to predict it.
answered Jan 2 at 16:01
movip1991movip1991
865
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
add a comment |
Estimating the execution time of an application or function is going to be difficult in any context. You might want to look up the halting problem for some insight to why. It's impossible to determine whether a given program will finish executing, and therefore, you can't really tell how long a given program will take to finish executing.
For general computing, varying hardware capabilities of any given system will always have an effect on the execution time of a program. Raspberry Pi is a little more discrete than that, and therefore more predictable in that sense, but those specifications will not always be consistent across its various versions. That adds to the complexity of determining a run time.
Practically, the most reliable way to determine how long a process will take would be to just run it and time it. If you absolutely need predicted times for something, you might be able to do a bit of a composite estimate - time the smaller chunks of the application separately, and then use those to determine how long you expect the application as a whole to run. For most situations, though, it would be much faster to just run the program itself rather than trying to predict it.
answered Jan 2 at 16:01
movip1991movip1991
865
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
add a comment |
Estimating the execution time of an application or function is going to be difficult in any context. You might want to look up the halting problem for some insight to why. It's impossible to determine whether a given program will finish executing, and therefore, you can't really tell how long a given program will take to finish executing.
For general computing, varying hardware capabilities of any given system will always have an effect on the execution time of a program. Raspberry Pi is a little more discrete than that, and therefore more predictable in that sense, but those specifications will not always be consistent across its various versions. That adds to the complexity of determining a run time.
Practically, the most reliable way to determine how long a process will take would be to just run it and time it. If you absolutely need predicted times for something, you might be able to do a bit of a composite estimate - time the smaller chunks of the application separately, and then use those to determine how long you expect the application as a whole to run. For most situations, though, it would be much faster to just run the program itself rather than trying to predict it.
answered Jan 2 at 16:01
movip1991movip1991
865
Estimating the execution time of an application or function is going to be difficult in any context. You might want to look up the halting problem for some insight to why. It's impossible to determine whether a given program will finish executing, and therefore, you can't really tell how long a given program will take to finish executing.
For general computing, varying hardware capabilities of any given system will always have an effect on the execution time of a program. Raspberry Pi is a little more discrete than that, and therefore more predictable in that sense, but those specifications will not always be consistent across its various versions. That adds to the complexity of determining a run time.
Practically, the most reliable way to determine how long a process will take would be to just run it and time it. If you absolutely need predicted times for something, you might be able to do a bit of a composite estimate - time the smaller chunks of the application separately, and then use those to determine how long you expect the application as a whole to run. For most situations, though, it would be much faster to just run the program itself rather than trying to predict it.
answered Jan 2 at 16:01
movip1991movip1991
865
answered Jan 2 at 16:01
movip1991movip1991
865
answered Jan 2 at 16:01
movip1991movip1991
865
answered Jan 2 at 16:01
movip1991movip1991
865
865
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
add a comment |
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
thank you, and it makes sense
– Ali Jaddoa
Jan 2 at 16:17
add a comment |
Store the time before and after the execution ? Then you could know the execution time
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
add a comment |
Store the time before and after the execution ? Then you could know the execution time
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
add a comment |
Store the time before and after the execution ? Then you could know the execution time
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
Store the time before and after the execution ? Then you could know the execution time
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
answered Jan 2 at 15:17
Liem Ly QuanLiem Ly Quan
4715
4715
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
add a comment |
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
thank you for the reply, but i need to estimate it in advance.
– Ali Jaddoa
Jan 2 at 15:29
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
What would the task be about ? I could imagine that there are cases where is is totally clueless about the time of completion of a task in advance (e.g: some network request). So know what it is about may help in prediction
– Liem Ly Quan
Jan 2 at 15:36
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
consider the application is face detection, so before I send the chosen image to the application I need to know, how long detecting faces in the image going to take.
– Ali Jaddoa
Jan 2 at 15:57
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f54008487%2fa-way-tool-to-make-an-estimation-of-execution-time-for-an-app-task%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
