-
Notifications
You must be signed in to change notification settings - Fork 419
Performance survey
Darknet Villain edited this page Apr 20, 2017
·
9 revisions
Please, share your i2pd experience with us.
E-mail supervillain@riseup.net if you wish to contribute anonymously.
| Hardware (board, CPU, RAM) | Operating system | Floodfill | CPU usage | RAM usage | Performance | Notes and comments |
|---|---|---|---|---|---|---|
| VPS, Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz, 512MB RAM | Ubuntu 14.04 | yes | 55% | 89MB | very good | |
| VPS, Intel(R) Xeon(R) CPU E5 @ 3GHz, 512MB RAM | Debian Jessie | no | 20% | 25MB | excellent | powers i2p.rocks in proxy |
| VPS, Intel(R) Xeon(R) CPU E5-2609 v2 @ 2.50GHz, 500MB RAM | Debian Jessie | no | 5% | 18MB | excellent | notransit=true, AESNI disabled, serves mid-range sized bittorrent tracker |
| Raspberry PI 1 | Debian Jessie | no | 20% - 90% | 15MB | good | runs small ircd, 90% cputime on startup, 5% to 20% on idle afterwards, notransit=true, ntcp=false uses this static build |
| Odroid U3 (4xA9 @ 1.6GHz,2GB) | Arch Linux ARM | no | 20% -60% | 55MB | excellent | transittunnels=512, bandwidth=O, elgamal=true; ~100 KiB/s, 43% tunnel success |
| Mac mini (PowerPC G4 @ 1.42 GHz, 1GB RAM) | Ubuntu Server 16.04.2 | no | 30%-60% | 58MB | very good | bandwidth=L, elgamal=true, transittunnels=512, 50% tunnel success |