From 2add3875884f9d8ef65cbd3d4d1dd1aa897d71ca Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Mon, 23 Mar 2015 17:37:07 +0000 Subject: -re benchmarking and adjusting MAX_QUEUE_PER_PEER --- src/fs/gnunet-service-fs_cp.h | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/src/fs/gnunet-service-fs_cp.h b/src/fs/gnunet-service-fs_cp.h index eca6ff1ed..5dee37a94 100644 --- a/src/fs/gnunet-service-fs_cp.h +++ b/src/fs/gnunet-service-fs_cp.h @@ -33,19 +33,16 @@ /** * Maximum number of outgoing messages we queue per peer. * - * Performance measurements for 2 peer setup for 50 MB file - * (with MAX_DATASTORE_QUEUE = 1 and RETRY_PROBABILITY_INV = 1): + * Performance measurements for 2 peer setup for 10 MB file + * (using perf_gnunet_service_fs_p2p): * - * 2: 1700 kb/s, 1372 kb/s - * 8: 2117 kb/s, 1284 kb/s, 1112 kb/s - * 16: 3500 kb/s, 3200 kb/s, 3388 kb/s - * 32: 3441 kb/s, 3163 kb/s, 3277 kb/s - * 128: 1700 kb/s; 2010 kb/s, 3383 kb/s, 1156 kb/s + * 24: 2-3 MB/s # ~ 24 MB RAM + * 256: 8 MB/s # ~256 MB RAM * - * Conclusion: 16 seems to be a pretty good value (stable - * and high performance, no excessive memory use). + * Conclusion: 24 should suffice (reasonable + * performance, no excessive memory use). */ -#define MAX_QUEUE_PER_PEER 16 +#define MAX_QUEUE_PER_PEER 24 /** * Length of the P2P success tracker. Note that having a very long -- cgit v1.2.3