I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Embedding update re: persistence

Browse Source
This commit is contained in:
zzz
2023-01-03 16:08:23 -05:00
parent ba4fa23d5d
commit a48879e014
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
i2p2www/pages/site/docs/applications/embedding.html
View File

@ -97,7 +97,20 @@ If you do this and your application gets hugely popular, it could break the netw
You must save the router's data (netdb, configuration, etc.) between runs of the router.
I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.
Even if you bundle router infos, I2P needs saved profile data for best performance.
Without persistence, your users will have a poor startup experience.
{%- endtrans %}</p>
<p>
There are two possibilities if you cannot provide persistence.
Either of these eliminates your project's load on our reseed servers and will significantly improve startup time.
</p><p>
1) Set up your own project reseed server(s) that serve much more than the usual number
of router infos in the reseed, say, several hundred. Configure the router to use only your servers.
</p><p>
2) Bundle one to two thousand router infos in your installer.
</p><p>
Also, delay or stagger your tunnel startup, to give the router a chance to integrate
before building a lot of tunnels.
</p>