Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit689bea8

Browse files
Moloejoegitbook-bot
authored andcommitted
GITBOOK-102: No subject
1 parent39658fb commit689bea8

File tree

1 file changed

+14
-17
lines changed

1 file changed

+14
-17
lines changed

‎pgml-cms/docs/introduction/apis/sql-extensions/pgml.deploy.md‎

Lines changed: 14 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -38,16 +38,15 @@ The default deployment behavior allows any algorithm to qualify. It's automatica
3838

3939
###Deploying the best score
4040

41-
\=== "SQL"
41+
####SQL
4242

43-
```sql
44-
SELECT*FROMpgml.deploy(
45-
'Handwritten Digit Image Classifier',
43+
<preclass="language-sql"><codeclass="lang-sql"><strong>SELECT * FROM pgml.deploy(
44+
</strong> 'Handwritten Digit Image Classifier',
4645
strategy => 'best_score'
4746
);
48-
```
47+
</code></pre>
4948

50-
\=== "Output"
49+
####Output
5150

5251
```sql
5352
project | strategy | algorithm
@@ -56,13 +55,11 @@ SELECT * FROM pgml.deploy(
5655
(1 row)
5756
```
5857

59-
\===
60-
6158
###**Specific Algorithms**
6259

6360
Deployment candidates can be restricted to a specific algorithm by including the`algorithm` parameter. This is useful when you're training multiple algorithms using different hyperparameters and want to restrict the deployment a single algorithm only:
6461

65-
\=== "SQL"
62+
####SQL
6663

6764
```sql
6865
SELECT*FROMpgml.deploy(
@@ -72,7 +69,7 @@ SELECT * FROM pgml.deploy(
7269
);
7370
```
7471

75-
\=== "Output"
72+
####Output
7673

7774
```sql
7875
project_name | strategy | algorithm
@@ -81,13 +78,13 @@ SELECT * FROM pgml.deploy(
8178
(1 row)
8279
```
8380

84-
\===
81+
8582

8683
###Rolling Back
8784

8885
In case the new model isn't performing well in production, it's easy to rollback to the previous version. A rollback creates a new deployment for the old model. Multiple rollbacks in a row will oscillate between the two most recently deployed models, making rollbacks a safe and reversible operation.
8986

90-
\=== "Rollback 1"
87+
####Rollback
9188

9289
```sql
9390
SELECT*FROMpgml.deploy(
@@ -96,7 +93,7 @@ SELECT * FROM pgml.deploy(
9693
);
9794
```
9895

99-
\=== "Output"
96+
####Output
10097

10198
```sql
10299
project | strategy | algorithm
@@ -105,7 +102,9 @@ SELECT * FROM pgml.deploy(
105102
(1 row)
106103
```
107104

108-
\=== "Rollback 2"
105+
####Rollback again
106+
107+
Rollbacks are actually new deployments, so issuing two rollbacks in a row will leave you back with the original model, making rollback safely undoable.
109108

110109
```sql
111110
SELECT*FROMpgml.deploy(
@@ -114,13 +113,11 @@ SELECT * FROM pgml.deploy(
114113
);
115114
```
116115

117-
\=== "Output"
116+
####Output
118117

119118
```sql
120119
project | strategy | algorithm
121120
------------------------------------+----------+-----------
122121
Handwritten Digit Image Classifier |rollback | xgboost
123122
(1 row)
124123
```
125-
126-
\===

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp