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: sources/platform/actors/development/programming_interface/actor_standby.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Traditional Actors are designed to run a single task and then stop. They're most
13
13
However, in some applications, waiting for an Actor to start is not an option. Actor Standby mode solves this problem by letting you have the Actor ready
14
14
in the background, waiting for the incoming HTTP requests. In a sense, the Actor behaves like a real-time web server or standard API server.
15
15
16
-
####How can I develop Actors using Standby mode
16
+
## How can I develop Actors using Standby mode
17
17
18
18
import Tabs from '@theme/Tabs';
19
19
import TabItem from '@theme/TabItem';
@@ -69,6 +69,6 @@ async def main() -> None:
69
69
Please make sure to describe your Actors, their endpoints, and the schema for their
70
70
inputs and ouputs in your README.
71
71
72
-
####Can I monetize my Actor in the Standby mode
72
+
## Can I monetize my Actor in the Standby mode
73
73
74
74
No, Standby mode is in Beta, and monetization is not supported.
Copy file name to clipboardExpand all lines: sources/platform/actors/running/actor_standby.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Traditional Actors are designed to run a single task and then stop. They're most
14
14
However, in some applications, waiting for an Actor to start is not an option. Actor Standby mode solves this problem by letting you have the Actor ready
15
15
in the background, waiting for the incoming HTTP requests. In a sense, the Actor behaves like a real-time web server or standard API server.
16
16
17
-
####How do I know if Standby mode is enabled?
17
+
## How do I know if Standby mode is enabled?
18
18
19
19
You will know that the Actor is enabled for Standby mode if you see the **Standby** tab on the Actor's detail page.
20
20
In the tab, you will find the hostname of the server, the description of the Actor's endpoints,
@@ -25,18 +25,18 @@ hit the API endpoint and get results.
Yes, you can still modify the input and click the Start button to run the Actor in normal mode. However, note that the Standby Actor might
31
31
not support this mode; the run might fail or return empty results. The normal mode is always supported in Standby Beta, even for Actors that don't handle
32
32
it well. Please head to the Actor README to learn more about the capabilities of your chosen Actor.
33
33
34
-
####Is there any scaling to accommodate the incoming requests
34
+
## Is there any scaling to accommodate the incoming requests
35
35
36
36
When you use the Actor in Standby mode, the system automatically scales the Actor to accommodate the incoming requests. Under the hood,
37
37
the system starts new Actor runs, which you will see in the Actor runs tab, with the origin set to Standby.
38
38
39
-
####How do I customize Standby configuration
39
+
## How do I customize Standby configuration
40
40
41
41
The Standby configuration currently consists of the following properties:
42
42
@@ -51,15 +51,15 @@ use the Actor-level hostname, this will always use the default configuration. To
51
51
You can then head to the Standby tab of the created Task and modify the configuration as needed. Note that the task has a specific hostname, so make
52
52
sure to use that in your application if you wish to use the custom configuration.
53
53
54
-
####Are the Standby runs billed differently
54
+
## Are the Standby runs billed differently
55
55
56
56
No, the Standby runs are billed in the same fashion as the normal runs.
57
57
However, running Actors in Standby mode might have unexpected costs, as the Actors run in the background and consume resources even when no requests are being sent until they are terminated after the idle timeout period.
58
58
59
-
####Are the Standby runs shared among users
59
+
## Are the Standby runs shared among users
60
60
61
61
No, even if you use the Actor-level hostname with the default configuration, the background Actor runs for your requests are not shared with other users.
62
62
63
-
####How can I develop Actors using Standby mode
63
+
## How can I develop Actors using Standby mode
64
64
65
65
See the [Actor Standby development section](../development/programming_interface/actor_standby.md).
0 commit comments