You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
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?
The text was updated successfully, but these errors were encountered: