Content
@
0 reply
20 recasts
20 reactions
Varun Srinivasan
@v
Hubble Replicator v2 We have a proposal for a new design to tackle the problems with the existing replicator. If you run a replicator today, we'd love to get your feedback on this. https://warpcast.notion.site/Replicator-v2-Public-6562ad1e6eef4c4ab2c27cf82aa759c1
9 replies
8 recasts
110 reactions
vhawk19.eth
@vhawk19
Issues am facing with current replicator setup - Backfill takes a long time (Public snapshots would help here) - Cannot prioritise certain messages over others - vv cpu intense, and cannot scale horizontally Is it possible to have multiple processors read from the event stream?
1 reply
0 recast
1 reaction
Hustor
@hustor
'vv cpu intense, and cannot scale horizontally' -- It's mainly because of the redis, can deploy redis independly.
0 reply
0 recast
0 reaction
