dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add memory clarification for components (#3684) 

* add memory clarification for components

Signed-off-by: yaron2 <schneider.yaron@live.com>

* clarification

Signed-off-by: yaron2 <schneider.yaron@live.com>

* formatting

Signed-off-by: yaron2 <schneider.yaron@live.com>

* examples

Signed-off-by: yaron2 <schneider.yaron@live.com>

* Update daprdocs/content/en/concepts/components-concept.md

Signed-off-by: Mark Fussell <markfussell@gmail.com>

---------

Signed-off-by: yaron2 <schneider.yaron@live.com>
Signed-off-by: Mark Fussell <markfussell@gmail.com>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
This commit is contained in:
Yaron Schneider 2023-08-17 22:25:18 -07:00 committed by GitHub
parent 9e6bc0ec60
commit 5173fd0c71
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
daprdocs/content/en/concepts/components-concept.md
View File

@ -19,6 +19,10 @@ As another example, the [pub/sub]({{< ref "pubsub-overview.md" >}}) building blo
You can get a list of current components available in the hosting environment using the `dapr components` CLI command.
{{% alert title="Note" color="primary" %}}
For any component that returns data to the app, it is recommended to set the memory capacity of the Dapr sidecar accordingly (process or container) to avoid potential OOM panics. For example in Docker use the `--memory` option. For Kubernetes, use the `dapr.io/sidecar-memory-limit` annotation. For processes this depends on the OS and/or process orchestration tools.*
{{% /alert %}}
## Component specification
Each component has a specification (or spec) that it conforms to. Components are configured at design-time with a YAML file which is stored in either: