public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Problems with "Enable some performance tuning" => extremly slow downloads
Date: Wed, 20 Feb 2019 11:18:04 +0100	[thread overview]
Message-ID: <325d9aee-15b5-d726-5af0-7d40509b47fb@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

Hi,

being curious, I tested commit
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=d03916e55851a243594ebf6f0c20c8f6d9092277
on my Core 127 / 32bit IPFire.

At first I didn't notice any differences, system was running as usual.
No important performance impact or change.

But yesterday, while starting some bigger downloads and closely
watching, I noticed that everytime someone started to download a
somewhat bigger file, e.g. 250-800 MB, downloading rates went down to a
crawl. Some downloads even aborted and nearly all where amazingly slow
(~150KB/s, normal: ~6.5 MB/s).

Restarting our Fritzbox and IPFire itself didn't help, all downloads
stayed that way.

After reverting the above commit in '/etc/sysctl.conf' and running
'sysctl -p', system is running at full speed again: VDSL, 50Mbit down /
10Mbit up.

Configuration:
Duo Box with Core 127/32bit. Running 'privoxy 3.0.28', 'squid 4.6'
(non-transparent, 512 MB RAM only), 'squidguard 1.5 beta',
'squidclamav', 'snort / guardian', 'unbound 1.9.0' with DoT/TFO.

Could someone please test and confirm (or not ;-) ).

Best,
Matthias

             reply	other threads:[~2019-02-20 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 10:18 Matthias Fischer [this message]
2019-02-20 15:40 ` Michael Tremer
2019-02-21  0:36   ` Matthias Fischer
2019-02-21  9:33     ` Michael Tremer
2019-02-21 15:41       ` Matthias Fischer
2019-02-22 17:40       ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=325d9aee-15b5-d726-5af0-7d40509b47fb@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox