Using hostd and rentd (more than one service) on the same host

[npelov]

Hi. I guess there is a reason for splitting to hostd, rentd, walletd, however in some cases more than one of those may be needed on a the same host. That complicates things a bit - different ports must be set, multiple interfaces must be accessed for different tasks. And one of the most important - requires multiple instances of consensus.db.
Have you considered of making consensusd or sianoded - a blockchain provider and an option for hostd, rentd, walletd to use it instead each of them having it's own blockchain? That would also be valid for multiple hostd instances. One host can run the node and hostd will just do the hosting.

[n8maninger]

We considered it, but the hard fork in June reduces the size of the blockchain stored on disk to a couple hundred MB. Very few users find it necessary to run more than one of the apps.

[npelov]

I read about that and I think it's great. What about the sync time. How does that work. Does each new node have to sync through the whole blockchain, discarding older data. I noticed that sync eats a lot of cpu power and bandwidth. I wouldn't mind saving those too. The sync took a day or two on my lowest spec machine and multiple hours on the highest spec. Would the hard fork update skip the full sync and somehow just sync the top of the blockchain?
Yes, technically instead bringing up new hosts the storage can be mounted as network volumes, but that introduces more points of failure. Bringing down a storage node for maintenance will block the hostd and it won't work until the storage node is up again. With multiple nodes each can be shut down individually, reducing the overall downtime.

Can you at least think about the points I made?