Git-Mirrors/Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2024-12-17 20:04:30 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated readme

Browse Source
This commit is contained in:
Mark Qvist 2022-06-10 13:13:51 +02:00
parent f74e6d12c9
commit d136eac32b
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -104,7 +104,9 @@ Currently, the following interfaces are supported:
- Custom hardware via stdio or pipes - Custom hardware via stdio or pipes
## Performance ## Performance
Reticulum targets a *very* wide usable performance envelope, but prioritises functionality and performance over low-bandwidth links. The goal is to provide a dynamic performance envelope from 250 bits per second, to 1 gigabit per second on normal hardware. Currently the usable performance envelope is approximately 500 bits per second to 20 megabits per second, with links faster than that not being saturated. Performance beyond the current level is planned for the future, but not highly prioritised at this point. Reticulum targets a *very* wide usable performance envelope, but prioritises functionality and performance over low-bandwidth links. The goal is to provide a dynamic performance envelope from 250 bits per second, to 1 gigabit per second on normal hardware.
Currently the usable performance envelope is approximately 500 bits per second to 20 megabits per second, with links faster than that not being saturated. Performance beyond the current level is planned for the future, but not highly prioritised at this point.
## Current Status ## Current Status
Reticulum should currently be considered beta software. All core protocol features are implemented and functioning, but additions will probably occur as real-world use is explored. There will be bugs. The API and wire-format can be considered relatively stable at the moment, but could change if warranted. Reticulum should currently be considered beta software. All core protocol features are implemented and functioning, but additions will probably occur as real-world use is explored. There will be bugs. The API and wire-format can be considered relatively stable at the moment, but could change if warranted.