Slow start up from cold start (20 minutes+), need help with logging all filesystem access with iotop
Well in my development suit I notice that currently the boot up of the full suit takes a long (too long) time - about 20 to 25 minutes before I can actually use the applications.
The far majority (15-20) minutes it is busy "after" booting ubuntu. When I try to start the following applications:
- postgres docker
- pgadmin server
- postman
- webstorm for front end
- webstorm for backend
- flow server for both front and backend.
- react-scripts-npm real time file tracker and updater for front end
Now the problem is: there are no logs available on what is actually taking most time. I installed iotop application and run that using sudo iotop -a -P before loading the development suit. However that only shows the currently alive processes.
I can see webstorm and flow constantly starting child processes that actually show 98+% "IO" wait time, however these processes are really short lived (a few seconds at most) so they don't show up in the end.
Can I let iotop show a total log, including processes that died, over a period of time?
startup disk-usage iotop
asked 11 hours ago
paul23paul23
1316
add a comment |
Well in my development suit I notice that currently the boot up of the full suit takes a long (too long) time - about 20 to 25 minutes before I can actually use the applications.
The far majority (15-20) minutes it is busy "after" booting ubuntu. When I try to start the following applications:
- postgres docker
- pgadmin server
- postman
- webstorm for front end
- webstorm for backend
- flow server for both front and backend.
- react-scripts-npm real time file tracker and updater for front end
Now the problem is: there are no logs available on what is actually taking most time. I installed iotop application and run that using sudo iotop -a -P before loading the development suit. However that only shows the currently alive processes.
I can see webstorm and flow constantly starting child processes that actually show 98+% "IO" wait time, however these processes are really short lived (a few seconds at most) so they don't show up in the end.
Can I let iotop show a total log, including processes that died, over a period of time?
startup disk-usage iotop
asked 11 hours ago
paul23paul23
1316
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
Edit your question and show mesudo fdisk -landfree -handswaponandsudo blkidandcat /etc/fstab. Report back to @heynnema oh... andls -al ~/.local/share/gnome-shell/extensions.
– heynnema
10 hours ago
add a comment |
Well in my development suit I notice that currently the boot up of the full suit takes a long (too long) time - about 20 to 25 minutes before I can actually use the applications.
The far majority (15-20) minutes it is busy "after" booting ubuntu. When I try to start the following applications:
- postgres docker
- pgadmin server
- postman
- webstorm for front end
- webstorm for backend
- flow server for both front and backend.
- react-scripts-npm real time file tracker and updater for front end
Now the problem is: there are no logs available on what is actually taking most time. I installed iotop application and run that using sudo iotop -a -P before loading the development suit. However that only shows the currently alive processes.
I can see webstorm and flow constantly starting child processes that actually show 98+% "IO" wait time, however these processes are really short lived (a few seconds at most) so they don't show up in the end.
Can I let iotop show a total log, including processes that died, over a period of time?
startup disk-usage iotop
asked 11 hours ago
paul23paul23
1316
Well in my development suit I notice that currently the boot up of the full suit takes a long (too long) time - about 20 to 25 minutes before I can actually use the applications.
The far majority (15-20) minutes it is busy "after" booting ubuntu. When I try to start the following applications:
- postgres docker
- pgadmin server
- postman
- webstorm for front end
- webstorm for backend
- flow server for both front and backend.
- react-scripts-npm real time file tracker and updater for front end
Now the problem is: there are no logs available on what is actually taking most time. I installed iotop application and run that using sudo iotop -a -P before loading the development suit. However that only shows the currently alive processes.
I can see webstorm and flow constantly starting child processes that actually show 98+% "IO" wait time, however these processes are really short lived (a few seconds at most) so they don't show up in the end.
Can I let iotop show a total log, including processes that died, over a period of time?
startup disk-usage iotop
startup disk-usage iotop
asked 11 hours ago
paul23paul23
1316
asked 11 hours ago
paul23paul23
1316
asked 11 hours ago
paul23paul23
1316
asked 11 hours ago
paul23paul23
1316
asked 11 hours ago
paul23paul23
1316
1316
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
Edit your question and show mesudo fdisk -landfree -handswaponandsudo blkidandcat /etc/fstab. Report back to @heynnema oh... andls -al ~/.local/share/gnome-shell/extensions.
– heynnema
10 hours ago
add a comment |
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
Edit your question and show mesudo fdisk -landfree -handswaponandsudo blkidandcat /etc/fstab. Report back to @heynnema oh... andls -al ~/.local/share/gnome-shell/extensions.
– heynnema
10 hours ago
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
Edit your question and show me
sudo fdisk -l and free -h and swapon and sudo blkid and cat /etc/fstab. Report back to @heynnema oh... and ls -al ~/.local/share/gnome-shell/extensions.– heynnema
10 hours ago
Edit your question and show me
sudo fdisk -l and free -h and swapon and sudo blkid and cat /etc/fstab. Report back to @heynnema oh... and ls -al ~/.local/share/gnome-shell/extensions.– heynnema
10 hours ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1122243%2fslow-start-up-from-cold-start-20-minutes-need-help-with-logging-all-filesyst%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 Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1122243%2fslow-start-up-from-cold-start-20-minutes-need-help-with-logging-all-filesyst%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
Is the 20 mins, from cold boot to desktop, or desktop to dev suite startup complete? If it's the later, can you start up one piece of dev suite at a time to determine which one may be causing the long startup time?
– heynnema
11 hours ago
It's the total time, about 2-3 minutes it takes to get to the login, then 2 more before desktop becomes responsive after logging in. Then almost all time (about 15-20) it takes for webstorm & flow (which are wrought together in the webstorm IDE, they just show as separate processes) to load.
– paul23
10 hours ago
Edit your question and show me
sudo fdisk -landfree -handswaponandsudo blkidandcat /etc/fstab. Report back to @heynnema oh... andls -al ~/.local/share/gnome-shell/extensions.– heynnema
10 hours ago