cyb-parity
cyb-parity copied to clipboard
Understand economics of interactions between browser and cybernode
The situation is the following:
- the are a lot of "free" cpu, ssd and networking resources left on cybernode
- feature set of current cybernode is ultimate for web3 apps but is not being used
Goal: We need to understand how much browser clients current cybernode cluster can serve to understand its economy better.
Scenario of usage by one user per day:
- IPFS cache. 300 files with even size
- Direct node's APIs: 5k requests
- Full text elastic search: 100 requests
- cyberd requests: 50 requests
- Structured elastic search: 1k requests
@xhipster
- ssd usage is high. With replication factor 1, we already have 1.5tb data. So, for replication factor 3, cybernode need about 5tb data on current solution.
- cpu usage is low, because currently there is no users. Right now cpu is used only for indexation ;(