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

In-memory storage for benchmarking #238

Open
haraldng opened this issue Jun 12, 2020 · 4 comments
Open

In-memory storage for benchmarking #238

haraldng opened this issue Jun 12, 2020 · 4 comments

Comments

@haraldng
Copy link

Hello,

I'm master student doing my thesis where I investigate in performance of distributed consensus algorithms. In the documentation it says that the in-memory storage cannot be bootstrapped. Is there any way to run a LogCabin cluster with in-memory storage for benchmarking?

@ongardie
Copy link
Member

Hi @haraldng, I don't know if there's an easy way to do that. It's sort of an unusual configuration, since most people want their data to be durable. Here are a couple of ideas:

  1. You could easily run with Segmented storage against a tmpfs.
  2. You might also be able to bootstrap the cluster with a Segmented storage member, then add a bunch of Memory storage members, then remove the original Segmented storage member.

@haraldng
Copy link
Author

I will try using tmpfs. Thank you for the advice!

@haraldng
Copy link
Author

Hi again,

Is the writeEx function used in the Benchmark example a blocking function? Blocking in terms of that it only returns to the client when a majority of Raft servers have committed that write operation?

@haraldng haraldng reopened this Jun 24, 2020
@ongardie
Copy link
Member

Is the writeEx function used in the Benchmark example a blocking function? Blocking in terms of that it only returns to the client when a majority of Raft servers have committed that write operation?

Yep. The client library is meant to be pretty hard to use unsafely.

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

No branches or pull requests

2 participants