Transactions PerformRead
Open
Nobody has claimed this yet.
area-transactions
Needs: triage :mag:
- Dominant language
- C#
- Stars
- 10.9k
- Forks
- 2.1k
- Avg merge
- 13h 56m
- Merged PRs (30d)
- 351
Description
I have been testing transactions in orleans, I used the BankAccount sample changed it to use mongodb as grain storage and noticed the following
every time PerformRead is called it actually write the current committed stated to the storage, is this correct ?
wouldn't it hurt the performance ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the BankAccount sample and reproduce the behavior using MongoDB as grain storage, focusing on calls to PerformRead. Trace whether each call writes the current committed state to storage; done means establishing whether this is intended and, if not, identifying the affected transaction and storage behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, mongodb
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100