Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction Model for Multi-threaded Implementation #118

Open
arpitbbhayani opened this issue Jun 13, 2024 · 5 comments
Open

Transaction Model for Multi-threaded Implementation #118

arpitbbhayani opened this issue Jun 13, 2024 · 5 comments
Assignees

Comments

@arpitbbhayani
Copy link
Contributor

We will base our transactional framework on the paper "VLL: a lock manager redesign for main memory database systems". By adopting a shared-nothing architecture and VLL, we can achieve multi-key operations without relying on mutexes or spinlocks.

@arpitbbhayani arpitbbhayani changed the title Transaction Model Transaction Model for Multi-threaded DiceDB Jun 13, 2024
@arpitbbhayani arpitbbhayani changed the title Transaction Model for Multi-threaded DiceDB Transaction Model for Multi-threaded Implementation Jul 12, 2024
@soumya-codes
Copy link
Contributor

soumya-codes commented Aug 3, 2024

@arpitbbhayani @JyotinderSingh @yashs360 can you please assign this to me. This sounds very interesting. I can get started with writing the design/implementation proposal for the same.

@JyotinderSingh
Copy link
Collaborator

@arpitbbhayani @JyotinderSingh @yashs360 can you please assign this to me. This sounds very interesting. I can get started with writing the design/implementation proposal for the same.

Assigned

@arpitbbhayani
Copy link
Contributor Author

Hello @soumya-codes,

There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.

We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.

Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.

Thanks again.

2 similar comments
@arpitbbhayani
Copy link
Contributor Author

Hello @soumya-codes,

There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.

We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.

Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.

Thanks again.

@arpitbbhayani
Copy link
Contributor Author

Hello @soumya-codes,

There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.

We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.

Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.

Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants