|
| 1 | +- model: notebooks.notebook |
| 2 | + pk: 2 |
| 3 | + fields: |
| 4 | + name: Welcome to PostgresML |
| 5 | + created_at: 2022-08-19 21:17:23.807438+00:00 |
| 6 | + updated_at: 2022-08-19 21:17:23.807451+00:00 |
| 7 | +- model: notebooks.notebookcell |
| 8 | + pk: 7 |
| 9 | + fields: |
| 10 | + notebook: 2 |
| 11 | + cell_type: 1 |
| 12 | + contents: "## Welcome!\n\nHi there. Welcome to what we hope is the future of machine |
| 13 | + learning!\n\nPostgresML is an end-to-end system for training and deploying real |
| 14 | + time machine learning models. It handles data versioning, model training, ranking, |
| 15 | + \nand safe production release. This dashboard gives an overview of what's happening |
| 16 | + in the system and also helps build and deploy experiments. The notebooks,\none |
| 17 | + of which you're reading right this moment, are our take on what ML notebooks |
| 18 | + could be when used with a real time data store like PostgreSQL.\n\n\n\n\n### |
| 19 | + Notebooks\n\nOur Notebooks are similar to Jupyter Notebooks, which you might |
| 20 | + be familiar with already. On the bottom of the page, you will find a text editor |
| 21 | + which is used to create new cells. Each cell can contain either Markdown which |
| 22 | + is just text really, and SQL which can be executed directly on this PostgresML |
| 23 | + instance.\n\nEach cell has a little menu in the top right corner, allowing you |
| 24 | + to (re)run it (if it's SQL), edit it, and delete it.\n\n\nLet me give you an |
| 25 | + example. The next cell (cell #2) will be a SQL cell which will execute a simple |
| 26 | + query." |
| 27 | + rendering: "<article class=\"markdown-body\"><h2>Welcome!</h2>\n<p>Hi there. Welcome |
| 28 | + to what we hope is the future of machine learning!</p>\n<p>PostgresML is an |
| 29 | + end-to-end system for training and deploying real time machine learning models. |
| 30 | + It handles data versioning, model training, ranking, \nand safe production release. |
| 31 | + This dashboard gives an overview of what's happening in the system and also |
| 32 | + helps build and deploy experiments. The notebooks,\none of which you're reading |
| 33 | + right this moment, are our take on what ML notebooks could be when used with |
| 34 | + a real time data store like PostgreSQL.</p>\n<h3>Notebooks</h3>\n<p>Our Notebooks |
| 35 | + are similar to Jupyter Notebooks, which you might be familiar with already. |
| 36 | + On the bottom of the page, you will find a text editor which is used to create |
| 37 | + new cells. Each cell can contain either Markdown which is just text really, |
| 38 | + and SQL which can be executed directly on this PostgresML instance.</p>\n<p>Each |
| 39 | + cell has a little menu in the top right corner, allowing you to (re)run it (if |
| 40 | + it's SQL), edit it, and delete it.</p>\n<p>Let me give you an example. The next |
| 41 | + cell (cell #2) will be a SQL cell which will execute a simple query.</p></article>" |
| 42 | + execution_time: null |
| 43 | + cell_number: 1 |
| 44 | + version: 1 |
| 45 | + deleted_at: null |
| 46 | +- model: notebooks.notebookcell |
| 47 | + pk: 8 |
| 48 | + fields: |
| 49 | + notebook: 2 |
| 50 | + cell_type: 3 |
| 51 | + contents: SELECT random(); |
| 52 | + rendering: "<div class=\"markdown-body\">\n<table>\n <thead>\n <tr>\n \n |
| 53 | + \ <td><strong>random</strong></td>\n \n </tr>\n </thead>\n <tbody>\n |
| 54 | + \ \n <tr>\n \n <td>0.6822832295608556</td>\n \n </tr>\n |
| 55 | + \ \n </tbody>\n</table>\n</div>\n" |
| 56 | + execution_time: '00:00:00.000654' |
| 57 | + cell_number: 2 |
| 58 | + version: 1 |
| 59 | + deleted_at: null |
| 60 | +- model: notebooks.notebookcell |
| 61 | + pk: 9 |
| 62 | + fields: |
| 63 | + notebook: 2 |
| 64 | + cell_type: 1 |
| 65 | + contents: 'I just asked Postgres to give me a random number. Pretty simple query, |
| 66 | + but it demonstrates the notebook functionality pretty well. You can see that |
| 67 | + the result of `random()` is currently `0.6822832295608556`. On the bottom right |
| 68 | + corner, you can see that it took `0:00:00.000654` or 0 hours, 0 minutes, 0 seconds |
| 69 | + and only 00006ns, which I believe is 0.6ms, for Postgres to run this query for |
| 70 | + us. This runtime is good to know, because you''ll be able to benchmark some |
| 71 | + of PostgresML functionality, including the models we provide, right here in |
| 72 | + these notebooks. |
| 73 | +
|
| 74 | +
|
| 75 | + Try rerunning the cell again by clicking the "play" button in the top right |
| 76 | + corner. You''ll see that the random number will change. Rerunning is a real |
| 77 | + time operation and Postgres will give you a different random number every time |
| 78 | + (otherwise it wouldn''t be random). |
| 79 | +
|
| 80 | +
|
| 81 | + #### Editing a cell |
| 82 | +
|
| 83 | +
|
| 84 | + You can edit a cell at any time, including SQL cells which will then run the |
| 85 | + new query immediately. |
| 86 | +
|
| 87 | +
|
| 88 | + #### Deleting a cell |
| 89 | +
|
| 90 | +
|
| 91 | + Deleting a cell is pretty easy: just click on the delete button in the top right |
| 92 | + corner. You''ll have 10 seconds to undo the delete if you so desire; we wouldn''t |
| 93 | + want you to lose your work because of an accidental click. |
| 94 | +
|
| 95 | +
|
| 96 | + #### Shortcuts |
| 97 | +
|
| 98 | +
|
| 99 | + The text editor supports the following helpful shortcuts: |
| 100 | +
|
| 101 | +
|
| 102 | +
|
| 103 | + | Shortcut | Description | |
| 104 | +
|
| 105 | + -----------| -------------------------------------- |
| 106 | +
|
| 107 | + | `Cmd-/` or `Ctrl-/` | Comment out SQL code. | |
| 108 | +
|
| 109 | + | `Cmd-Enter` or `Ctrl-Enter` | Save/create a cell.| |
| 110 | +
|
| 111 | +
|
| 112 | + By the way, this was a Markdown table, you can make those here as well.' |
| 113 | + rendering: '<article class="markdown-body"><p>I just asked Postgres to give me |
| 114 | + a random number. Pretty simple query, but it demonstrates the notebook functionality |
| 115 | + pretty well. You can see that the result of <code>random()</code> is currently |
| 116 | + <code>0.6822832295608556</code>. On the bottom right corner, you can see that |
| 117 | + it took <code>0:00:00.000654</code> or 0 hours, 0 minutes, 0 seconds and only |
| 118 | + 00006ns, which I believe is 0.6ms, for Postgres to run this query for us. This |
| 119 | + runtime is good to know, because you''ll be able to benchmark some of PostgresML |
| 120 | + functionality, including the models we provide, right here in these notebooks.</p> |
| 121 | +
|
| 122 | + <p>Try rerunning the cell again by clicking the "play" button in the top right |
| 123 | + corner. You''ll see that the random number will change. Rerunning is a real |
| 124 | + time operation and Postgres will give you a different random number every time |
| 125 | + (otherwise it wouldn''t be random).</p> |
| 126 | +
|
| 127 | + <h4>Editing a cell</h4> |
| 128 | +
|
| 129 | + <p>You can edit a cell at any time, including SQL cells which will then run |
| 130 | + the new query immediately.</p> |
| 131 | +
|
| 132 | + <h4>Deleting a cell</h4> |
| 133 | +
|
| 134 | + <p>Deleting a cell is pretty easy: just click on the delete button in the top |
| 135 | + right corner. You''ll have 10 seconds to undo the delete if you so desire; we |
| 136 | + wouldn''t want you to lose your work because of an accidental click.</p> |
| 137 | +
|
| 138 | + <h4>Shortcuts</h4> |
| 139 | +
|
| 140 | + <p>The text editor supports the following helpful shortcuts:</p> |
| 141 | +
|
| 142 | + <table> |
| 143 | +
|
| 144 | + <thead> |
| 145 | +
|
| 146 | + <tr> |
| 147 | +
|
| 148 | + <th>Shortcut</th> |
| 149 | +
|
| 150 | + <th>Description</th> |
| 151 | +
|
| 152 | + </tr> |
| 153 | +
|
| 154 | + </thead> |
| 155 | +
|
| 156 | + <tbody> |
| 157 | +
|
| 158 | + <tr> |
| 159 | +
|
| 160 | + <td><code>Cmd-/</code> or <code>Ctrl-/</code></td> |
| 161 | +
|
| 162 | + <td>Comment out SQL code.</td> |
| 163 | +
|
| 164 | + </tr> |
| 165 | +
|
| 166 | + <tr> |
| 167 | +
|
| 168 | + <td><code>Cmd-Enter</code> or <code>Ctrl-Enter</code></td> |
| 169 | +
|
| 170 | + <td>Save/create a cell.</td> |
| 171 | +
|
| 172 | + </tr> |
| 173 | +
|
| 174 | + </tbody> |
| 175 | +
|
| 176 | + </table> |
| 177 | +
|
| 178 | + <p>By the way, this was a Markdown table, you can make those here as well.</p></article>' |
| 179 | + execution_time: null |
| 180 | + cell_number: 3 |
| 181 | + version: 1 |
| 182 | + deleted_at: null |
| 183 | +- model: notebooks.notebookcell |
| 184 | + pk: 10 |
| 185 | + fields: |
| 186 | + notebook: 2 |
| 187 | + cell_type: 1 |
| 188 | + contents: '### Thank you |
| 189 | +
|
| 190 | +
|
| 191 | + Thank you for trying out PostgresML! We hope you enjoy your time here and have |
| 192 | +
|
| 193 | + fun learning about machine learning, in the comfort of your favorite database.' |
| 194 | + rendering: '<article class="markdown-body"><h3>Thank you</h3> |
| 195 | +
|
| 196 | + <p>Thank you for trying out PostgresML! We hope you enjoy your time here and |
| 197 | + have |
| 198 | +
|
| 199 | + fun learning about machine learning, in the comfort of your favorite database.</p></article>' |
| 200 | + execution_time: null |
| 201 | + cell_number: 4 |
| 202 | + version: 1 |
| 203 | + deleted_at: null |
| 204 | +- model: notebooks.notebookcell |
| 205 | + pk: 11 |
| 206 | + fields: |
| 207 | + notebook: 2 |
| 208 | + cell_type: 3 |
| 209 | + contents: SELECT 'Have a nice day!' AS greeting; |
| 210 | + rendering: "<div class=\"markdown-body\">\n<table>\n <thead>\n <tr>\n \n |
| 211 | + \ <td><strong>greeting</strong></td>\n \n </tr>\n </thead>\n <tbody>\n |
| 212 | + \ \n <tr>\n \n <td>Have a nice day!</td>\n \n </tr>\n |
| 213 | + \ \n </tbody>\n</table>\n</div>\n" |
| 214 | + execution_time: '00:00:00.000580' |
| 215 | + cell_number: 5 |
| 216 | + version: 1 |
| 217 | + deleted_at: null |
0 commit comments