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

Hardware investigation #5

Open
junszhao opened this issue Jun 6, 2022 · 1 comment
Open

Hardware investigation #5

junszhao opened this issue Jun 6, 2022 · 1 comment
Assignees

Comments

@junszhao
Copy link
Contributor

junszhao commented Jun 6, 2022

To continue the MPC experiments, we need new hardware.

We also need some new hardware to host public solid web apps.

Can we use Ghent's set-up as the starting point?

@renyuneyun
Copy link
Member

renyuneyun commented Jun 6, 2022

I guess we can start with their hardware as a very basic starting point, if they allow.
But as far as I understand from KNowledgeOnWebScale/solid-calendar-store#31, each user needs their own server process if we want to deploy the calendar, which makes the management complicated and resource consumption (mainly memory) bigger.
And we also need to consider how the DNS is done -- each user is assigned a sub-domain? Or should we use a same domain/hostname with each user in a sub-folder (the default situation for CSS)?

For MPC experiments, that depends on what resources are available from Ghent's system. We need to use a library MP-SPDZ, and install some dependencies. Alternatively, we could use Docker containers.
In fact, Nitin and I are planning to use Docker containers to isolate each node, and assign different network properties to them to see if we can make some more interesting benchmarks. So hope we can create (and therefore manage) Docker containers in the server...

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