You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,9 @@ To run the program on the Google Cloud platform you have to create a new project
80
80
And if you haven't done it yet you have to enable billing for the project.
81
81
82
82
The first step is to do the setup of the notebook environment variables. You will be asked to enable access to your Google Drive and Google credentials.
83
+
83
84

85
+
84
86
Then you need to fill the file that is created in the root of your google drive with your project id and the name you want to give the bucket.
85
87
86
88
Finally run all the cells in *Setup environment*, this will create a new bucket and all the the *./data* files are copied into it. It also create a new directory (*./bucket*) on the Colab runtime that is directly binded to the cloud storage bucket.
@@ -113,6 +115,7 @@ Runs:
113
115
* 5 workers, 20 cores, 8k test image
114
116
115
117

118
+
116
119
As you can see by doubling the number of cores the execution time is reduced by about half each time.
117
120
118
121
#### Weak scalability
@@ -129,6 +132,7 @@ Runs:
129
132
* 4 workers, 16 cores, 8k image
130
133
131
134

135
+
132
136
As you can see the execution is always around 4 minutes.
0 commit comments