Google Colab : Local Runtime use
I was currently using google-colab and on the getting started pages, we see:
Local runtime support Colab supports connecting to a Jupyter runtime
on your local machine. For more information, see our documentation.
So, when I saw the documentation I connected my colab notebook to the local runtime, after the installations,etc by using the connected tab.
And when I access the memory info:
!cat /proc/meminfo
The output is as follows:
MemTotal: 3924628 kB
MemFree: 245948 kB
MemAvailable: 1473096 kB
Buffers: 168560 kB
Cached: 1280300 kB
SwapCached: 20736 kB
Active: 2135932 kB
Inactive: 991300 kB
Active(anon): 1397156 kB
Inactive(anon): 560124 kB
Active(file): 738776 kB
Inactive(file): 431176 kB
Unevictable: 528 kB
Mlocked: 528 kB
Which is the memory info for my pc, so certainly the access from the notebook is to my pc? Then how is it any different from my local jupyter-notebook? Now, I can't use the high memory environment of 13 Gigs, nor can I have GPU access.
Would be great if someone can explain!
google-colaboratory
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
add a comment |
I was currently using google-colab and on the getting started pages, we see:
Local runtime support Colab supports connecting to a Jupyter runtime
on your local machine. For more information, see our documentation.
So, when I saw the documentation I connected my colab notebook to the local runtime, after the installations,etc by using the connected tab.
And when I access the memory info:
!cat /proc/meminfo
The output is as follows:
MemTotal: 3924628 kB
MemFree: 245948 kB
MemAvailable: 1473096 kB
Buffers: 168560 kB
Cached: 1280300 kB
SwapCached: 20736 kB
Active: 2135932 kB
Inactive: 991300 kB
Active(anon): 1397156 kB
Inactive(anon): 560124 kB
Active(file): 738776 kB
Inactive(file): 431176 kB
Unevictable: 528 kB
Mlocked: 528 kB
Which is the memory info for my pc, so certainly the access from the notebook is to my pc? Then how is it any different from my local jupyter-notebook? Now, I can't use the high memory environment of 13 Gigs, nor can I have GPU access.
Would be great if someone can explain!
google-colaboratory
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
add a comment |
I was currently using google-colab and on the getting started pages, we see:
Local runtime support Colab supports connecting to a Jupyter runtime
on your local machine. For more information, see our documentation.
So, when I saw the documentation I connected my colab notebook to the local runtime, after the installations,etc by using the connected tab.
And when I access the memory info:
!cat /proc/meminfo
The output is as follows:
MemTotal: 3924628 kB
MemFree: 245948 kB
MemAvailable: 1473096 kB
Buffers: 168560 kB
Cached: 1280300 kB
SwapCached: 20736 kB
Active: 2135932 kB
Inactive: 991300 kB
Active(anon): 1397156 kB
Inactive(anon): 560124 kB
Active(file): 738776 kB
Inactive(file): 431176 kB
Unevictable: 528 kB
Mlocked: 528 kB
Which is the memory info for my pc, so certainly the access from the notebook is to my pc? Then how is it any different from my local jupyter-notebook? Now, I can't use the high memory environment of 13 Gigs, nor can I have GPU access.
Would be great if someone can explain!
google-colaboratory
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
I was currently using google-colab and on the getting started pages, we see:
Local runtime support Colab supports connecting to a Jupyter runtime
on your local machine. For more information, see our documentation.
So, when I saw the documentation I connected my colab notebook to the local runtime, after the installations,etc by using the connected tab.
And when I access the memory info:
!cat /proc/meminfo
The output is as follows:
MemTotal: 3924628 kB
MemFree: 245948 kB
MemAvailable: 1473096 kB
Buffers: 168560 kB
Cached: 1280300 kB
SwapCached: 20736 kB
Active: 2135932 kB
Inactive: 991300 kB
Active(anon): 1397156 kB
Inactive(anon): 560124 kB
Active(file): 738776 kB
Inactive(file): 431176 kB
Unevictable: 528 kB
Mlocked: 528 kB
Which is the memory info for my pc, so certainly the access from the notebook is to my pc? Then how is it any different from my local jupyter-notebook? Now, I can't use the high memory environment of 13 Gigs, nor can I have GPU access.
Would be great if someone can explain!
google-colaboratory
google-colaboratory
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
asked Nov 28 '18 at 7:29
aspiring1aspiring1
559
559
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The main advantages to using Colab with a local backend stem from Drive-based notebook storage: Drive commenting, ACLs, and easy link-based sharing of the finished notebook.
When using Jupyter, sharing notebooks requires sharing files. And, accessing your notebooks from a distinct machine requires installing Jupyter rather than loading a website.
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
add a comment |
The only benefit is to keep your notebooks in Google Drive.
- you can share them easily
- you have automatic history/versioning
- people can comment on your notebooks
You also have headings with collapsible outline, and probably cleaner UI (if you prefer Colab styling).
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
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%2f53514243%2fgoogle-colab-local-runtime-use%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
The main advantages to using Colab with a local backend stem from Drive-based notebook storage: Drive commenting, ACLs, and easy link-based sharing of the finished notebook.
When using Jupyter, sharing notebooks requires sharing files. And, accessing your notebooks from a distinct machine requires installing Jupyter rather than loading a website.
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
add a comment |
The main advantages to using Colab with a local backend stem from Drive-based notebook storage: Drive commenting, ACLs, and easy link-based sharing of the finished notebook.
When using Jupyter, sharing notebooks requires sharing files. And, accessing your notebooks from a distinct machine requires installing Jupyter rather than loading a website.
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
add a comment |
The main advantages to using Colab with a local backend stem from Drive-based notebook storage: Drive commenting, ACLs, and easy link-based sharing of the finished notebook.
When using Jupyter, sharing notebooks requires sharing files. And, accessing your notebooks from a distinct machine requires installing Jupyter rather than loading a website.
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
The main advantages to using Colab with a local backend stem from Drive-based notebook storage: Drive commenting, ACLs, and easy link-based sharing of the finished notebook.
When using Jupyter, sharing notebooks requires sharing files. And, accessing your notebooks from a distinct machine requires installing Jupyter rather than loading a website.
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
answered Nov 28 '18 at 14:16
Bob SmithBob Smith
8,20542132
8,20542132
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
add a comment |
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
Instead of drive commenting, we can have commenting on github too, I guess which is better, since there we can create issues and stuff to get work done.
– aspiring1
Nov 29 '18 at 6:12
add a comment |
The only benefit is to keep your notebooks in Google Drive.
- you can share them easily
- you have automatic history/versioning
- people can comment on your notebooks
You also have headings with collapsible outline, and probably cleaner UI (if you prefer Colab styling).
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
add a comment |
The only benefit is to keep your notebooks in Google Drive.
- you can share them easily
- you have automatic history/versioning
- people can comment on your notebooks
You also have headings with collapsible outline, and probably cleaner UI (if you prefer Colab styling).
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
add a comment |
The only benefit is to keep your notebooks in Google Drive.
- you can share them easily
- you have automatic history/versioning
- people can comment on your notebooks
You also have headings with collapsible outline, and probably cleaner UI (if you prefer Colab styling).
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
The only benefit is to keep your notebooks in Google Drive.
- you can share them easily
- you have automatic history/versioning
- people can comment on your notebooks
You also have headings with collapsible outline, and probably cleaner UI (if you prefer Colab styling).
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
answered Nov 28 '18 at 14:49
Korakot ChaovavanichKorakot Chaovavanich
3,55621740
3,55621740
add a comment |
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%2f53514243%2fgoogle-colab-local-runtime-use%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
