Skip to content

Efficiently performing read only operation on entity #2053

Answered by cgillum
TurakKatase asked this question in Q&A
Discussion options

You must be logged in to vote

I think the reason this creates a performance bottleneck is because each IsEnabled check from your orchestration(s) to the entity is represented as a series of messages that need to be processed by the entity. The entity can only process one message at a time, which means it slows down as you add more orchestrations.

You might be able to speed this up quite a bit by using IDurableEntityClient in an activity function that fetches the read-only state of the entity (which is very fast). It still involves messaging because you have to invoke an activity function, but it's more scalable since it removes the entity operation throughput bottleneck. This option should be viable as long as you can…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@TurakKatase
Comment options

Answer selected by TurakKatase
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants