Personal proxy not honoring buffer size settings
Toomas Aas <[email protected]> Tue, 18 Feb 2014 21:00:30 +0200
| Newsgroups | gmane.comp.distributed-net.rc5 |
|---|---|
| Message-ID | <[email protected]> |
Hello! I've been running a personal proxy for almost as long as I've been involved in distributed.net, which is since 1997. The current version that I have is build 347 running on FreeBSD 7.4. For last several years I've been concentrating mostly on OGR. My clients are configured to work on OGR whenever possible and only fall back to RC5 in case of network problems, so I have rarely done any RC5 blocks. Accordingly, I had limits in proxyper.ini set like this: [rc5-72] minkeysready=5 maxkeysready=400 maxkeysdone=5 [ogrng] minkeysready=34 maxkeysready=2400 maxkeysdone=34 Given my client settings, this resulted in proxy connecting to fullserver whenever it had 34 OGR blocks in its out-buffer, which was typically once in an hour or so. Now that we are out of OGR work, all my clients started working on RC5, so I adjusted the buffer size settings accordingly: [rc5-72] minkeysready=100 maxkeysready=7200 maxkeysdone=100 However, this does not have the desired effect. Instead of waiting until 100 blocks have been gathered in the rc5 out-buffer, the proxy connects to upstream server every couple of minutes when it has only few RC5 blocks to return: $ grep "Last uplink" console20140218.log 2014-02-18 00:09:40,Status: rc5-72: Last uplink sent 2 and received 0 2014-02-18 00:09:40,Status: ogrng: Last uplink sent 0 and received 0 2014-02-18 00:12:59,Status: rc5-72: Last uplink sent 5 and received 0 2014-02-18 00:12:59,Status: ogrng: Last uplink sent 0 and received 0 2014-02-18 00:15:40,Status: rc5-72: Last uplink sent 2 and received 0 2014-02-18 00:15:40,Status: ogrng: Last uplink sent 0 and received 0 2014-02-18 00:18:42,Status: rc5-72: Last uplink sent 6 and received 0 2014-02-18 00:18:42,Status: ogrng: Last uplink sent 0 and received 0 ... etc I modified the configuration of my personal proxy this morning and thought that maybe it needs some time to "settle in", but 12 hours later the situation seems unchanged. I don't want to DoS the upstream keyservers with my constant connection attempts, but I don't know how to stop this. I tried adding 'expertmode=1' to the [rc5-72] section, but this doesn't help. -- Toomas Aas participant #32,484 _______________________________________________ rc5 mailing list rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] http://lists.distributed.net/mailman/listinfo/rc5