Hello, I have two issues:
1) We just switched to new orbit-db and I noticed that the behaviour of
replicated event changed.
I have a simple test - one node adds 1000 entries to its local log db, second node connects and replicates this db.
Previously (orbit-db < 0.27) I was receiving
replicated event every ~32 entries (smaller chunks).
Now I get only one big chunk and one
replicated event after all 1000 entries are done being replicated.
Is it an expected behaviour? Is there a way to send smaller chunks as before?
2) What times of replication I should expect after upgrading orbit-db, ipfs etc.?
Currently we experience ~20 seconds for localhost p2p network and ~150 seconds for tor network:
https://github.com/ZbayApp/waggle/runs/4326485402?check_suite_focus=true (both 1000 entries).
The times are very similar to what was before:
replicatedevent: indeed, this is now sent only when the db has been (fully) replicated. in fact, the previous behaviour wasn't intended (replicated events "chunked"). however, if I understand the need described above, you want to be able to "know when some progress of replication has been made" and the
replicate.progressevent will give you that (see https://github.com/orbitdb/orbit-db-store/blob/main/src/Store.js#L100 for the callback signature and params). it's emitted for each replicated db log entry. with that, you can eg. show a nice progress bar, or hook to it to show the replicated data to the user. note though that when
replicate.progressis fired, the DB index hasn't been updated yet with the replicated data.