logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-02 14:13:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

store queries

Browse Source
This commit is contained in:
kaichaosun 2024-09-26 10:50:31 +08:00
parent 6afa79a5a5
commit fe19b87ea4
No known key found for this signature in database
GPG Key ID: 223E0F992F4F03BF
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
standards/application/bandwidth-optimization.md
View File

@ -78,7 +78,13 @@ _Concerns:_
**Option 3**
Increase the time interval between message retransmissions to reduce bandwidth usage.
Increase the time interval between message retransmissions to reduce bandwidth usage. The current resend epoch calculation in Status app is as follows:
```
next_epoch = current_epoch + (2^(send_count−1)×30×3) + rand(0,30)
```
The interval can be increased by adjusting the constant factor (30) to a higher value, e.g., 60 or 90, to reduce the frequency of message retransmissions.
_Concerns:_
- it may increase the latency of message delivery.
@ -94,11 +100,14 @@ In the long term, such messages should persisted and updated with a decentralize
In the short term, the application should optimize the frequency of updates and reduce the size of descriptive messages to minimize bandwidth usage, for example only publish the id or hash of the message content, store the original content in other places like IPFS or S3.
### Store Node Queries
### Store Node Queries for missing messages and messages sent check
Regular queries to store nodes for missing messages can create additional network traffic.
Regular queries to store nodes can create additional network traffic.
**Option 1**
Use e2e reliability for missing messages retrieval and messages sent check.
Use e2e reliability for missing messages retrieval.
### Device Synchronization