Bug 11096 - speedproblems Download
Summary: speedproblems Download
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: x86_64 Windows
: - Unknown - - Unknown -
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-15 09:52 UTC by DJ-Melo
Modified: 2018-09-25 11:31 UTC (History)
4 users (show)

See Also:


Attachments
cpu usage (122.36 KB, image/png)
2016-04-25 11:22 UTC, DJ-Melo
Details
vmware log (280.60 KB, text/plain)
2016-04-25 11:22 UTC, DJ-Melo
Details
screen1 (204.15 KB, image/png)
2016-07-21 08:26 UTC, DJ-Melo
Details
screen2 (204.87 KB, image/png)
2016-07-21 08:26 UTC, DJ-Melo
Details
screen3 (43.54 KB, image/png)
2016-07-21 08:27 UTC, DJ-Melo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description DJ-Melo 2016-04-15 09:52:24 UTC
downloadspeed is only 5 MB normaly 15MB.

downgrade to backup of the vm to core 99 all works normal and fast.

VM is Vmware Workstation 12.0.1 Ipfire run's in 64 Bit, also with core 100 and a pae Kernel 32 bit I've tested the newest update's again the result is the same. Only 5 MB on Core 100. With the Core 99 machine no speed problems. The Machine uses vmxnet3 Adapters. I'm using squid, clamav, urlfilter.

http://fireinfo.ipfire.org/profile/23d87c9a8b1f8d8d0b82d40dd1afc7fcfdd55965


Any Ideas?

Greetings DJ
Comment 1 DJ-Melo 2016-04-22 14:46:12 UTC
also with 12.1.1 same problem. Core 99 works with fullspeed
Comment 2 Michael Tremer 2016-04-22 16:54:20 UTC
Do you have any more details about this? CPU usage? Logs from the VM and/or hypervisor? Otherwise this would just be guessing.
Comment 3 DJ-Melo 2016-04-25 11:22:05 UTC
Created attachment 434 [details]
cpu usage
Comment 4 DJ-Melo 2016-04-25 11:22:43 UTC
Created attachment 435 [details]
vmware log
Comment 5 DJ-Melo 2016-04-27 09:04:11 UTC
core 101 x64 in testing same problem.

Do you need anything else?
Comment 6 DJ-Melo 2016-04-27 09:11:33 UTC
without squiod on green 8 MB with squid 3-5 MB

Squid uses 2048 MB RAM
Comment 7 DJ-Melo 2016-04-27 09:28:28 UTC
interesting is not on all servers the speed is low.

a download from heise.de runs with 15 MB

winfuture or opensuse only with 5 MB

on Core 99 all is 15 MB

is it possible this is a DNS Problem? I'm using google's DNS on both machines.
Comment 8 DJ-Melo 2016-05-17 14:43:56 UTC
I've installed the newest Core 102 x64 NOT as a VM on the same machine. The Result was Download 8 MB/s. Than i've installed core 99 on the same machine hard. The Result was 19 MB/s.
Comment 9 Michael Tremer 2016-05-17 15:07:35 UTC
@Arne: Could you have a look at this?
Comment 10 DJ-Melo 2016-05-30 14:17:17 UTC
unter http://fireinfo.ipfire.org/profile/ea6805bc821925a317e49698c113a1aca857876b

win 10 als host mit aktueller Virtualbox das gleiche Problem

A1SRM-2558F von Supermicro ist das Host Board

sowohl Core 102_x64 als auch Core102 32bit

Core 99 läut unaufällig und sogar perfomanter als mit VMWare Workstation virtualisiert.
Comment 11 DJ-Melo 2016-06-17 16:07:59 UTC
under http://fireinfo.ipfire.org/profile/ea6805bc821925a317e49698c113a1aca857876b

win 10 as host with current Virtualbox the same problem

A1SRM-2558F Supermicro is the host board

both Core 102_x64 and Core102 32bit

Core 99 runs inconspicuously and even perfomanter as virtualized with VMWare Workstation.

Core 103 trial problem still exists.
Comment 12 DJ-Melo 2016-06-23 10:37:58 UTC
sorry here http://fireinfo.ipfire.org/profile/380d750e719d1cc8dec13314a0979cd32fcf112f is the correct hardware profile
Comment 13 Arne.F 2016-07-19 15:13:39 UTC
I still not have a good Idea. 

You can try to manually install the old kernel to test if this is a kernel or a userspace problem but maybee the old kernel has missing features. 

cd /opt/pakfire/tmp
wget http://mirror0.ipfire.org/pakfire2/2.17/paks/linux-pae-3.14.43-62.ipfire
gpg -d < linux-pae-3.14.43-62.ipfire > kernel.tar
tar xvf kernel.tar
./install.sh

Check grub config before reboot!
Comment 14 DJ-Melo 2016-07-20 21:00:00 UTC
Sorry that doese not work. The Kernel isn't booting.
Comment 15 DJ-Melo 2016-07-21 08:24:48 UTC
(In reply to dj-melo from comment #14)
> Sorry that doese not work. The Kernel isn't booting.

plese have a look at screens 1-3
Comment 16 DJ-Melo 2016-07-21 08:26:14 UTC
Created attachment 459 [details]
screen1
Comment 17 DJ-Melo 2016-07-21 08:26:44 UTC
Created attachment 460 [details]
screen2
Comment 18 DJ-Melo 2016-07-21 08:27:15 UTC
Created attachment 461 [details]
screen3
Comment 19 Arne.F 2016-08-04 11:20:03 UTC
Ups. This cannot work with the 64bit installation. The old kernel is 32bit.

You can also try a actual nightly with kernel 3.14.74 but i fear that this also not helps.
Comment 20 DJ-Melo 2016-08-10 20:05:55 UTC
The problem is in the trial Core 104 unfortunately still so true your advertisment "too fast networks and the use of embedded systems are no problem for IPFire." Unfortunately no longer. very unfortunate. Is there realy no one with the problem?
Comment 21 DJ-Melo 2016-09-01 12:06:36 UTC
Hi,

by collective upgrade UM to 200/20 Mbit with new 6490 Cable under Core99 32 bit everything nice!really fun.

Full of hope I updated to Core 103 32 bit... again same problems. So Squid and QoS off from then go not even the 50 Mbit ...

Please, please, look at that more closely at it but can not be that since since April does nothing.

P.S:

new information:

I let my UM fritzbox 6360 in bridge run so I have under Core 99 169 Mbit ind speedof.me (shows me the fritzbox than max capacity)

Core 103 32 bit 50 Mbit.

the download speeds are my Firefox displays appropriately.

in Core 99 i must stop Qos to get the full speed. In Core 103/104 makes no difference. Can this possibly still be an approach?

greetings
Comment 22 DJ-Melo 2016-09-15 15:54:41 UTC
Core 104 Testing with 79. Kernel Problem stilkl the same
Comment 23 DJ-Melo 2016-09-16 13:25:10 UTC
Core 104 64 bit with 79. kernel same problem
Comment 24 Michael 2016-09-28 13:00:39 UTC
Hi,

As per request to add my own comments and experiences:

Currently still running core 102 I noticed that I get a very low download rate with my 100MBit cable provider (Vodafone). Just about 32MBit was possible at that moment.

After changing my LAN configuration and bypassing IPFire, I reached the peak of about 99 up to 100 MBit and even slightly more.

Hence, IPFire must be the cause of this slow connection and since I know QoS a little bit, I started digging at this place. 

The QoS service/daemon was not running all the time. I had it once set up for testing purposes but it was DISABLED for quite a long time.

While testing I've set up (or was it done automatically by some templates? Don't remember anymore) some classes for VPN and webtraffic. Some of those classes were limited to the Maximum value of 32000, exactly the download rate I got so far. So it was quite clear that this is the cause for my current Limit.

After changing those limits at the various classes to the value of 100000 the download rate increased immediately.

Please note: QoS is still NOT running right now AND I do not use any VM, just good old plain hardware CoreDuo Xeon, 4GB RAM.

So I guess a deactivated QoS still Counts and uses those set up classes, right?

Pls. see: http://forum.ipfire.org/viewtopic.php?f=22&t=17285&p=100898

Michael
Comment 25 Tom 2016-10-12 16:56:51 UTC
I'm experiencing the same problem with Steam-Downloads, at least there I realized the issue first. Running build 105, downloading ISOs are NOT affected (tested with Ubuntu ISO). Download cap is around 12-16MBit where I usually get between 45-65MBit. System load on the fire explodes and user activity is using >70% cpu time.
imho this is a bug either in squid or squidclam as disabling the proxy or at least squidclam was the solution for me.
Comment 26 DJ-Melo 2016-10-19 10:43:12 UTC
Is there any chance that the problem in Core 106 will have fixed, and how does it work with the openssl bug?
Comment 27 DJ-Melo 2016-10-22 10:48:28 UTC
Core 106 32 Bit same problem. The DNS resolving is even slower than before i think

dns server are public dns of google.
Comment 28 DJ-Melo 2016-10-24 11:04:49 UTC
if I deactivate squid on green completely the speed with core 106 is not super but ok. so i think the problem is squid or even in this way. with squid on not transparent the rate is only 65 mbit.
Comment 29 Tom 2016-10-24 13:18:19 UTC
(In reply to dj-melo from comment #28)
> if I deactivate squid on green completely the speed with core 106 is not
> super but ok. so i think the problem is squid or even in this way. with
> squid on not transparent the rate is only 65 mbit.

Do you need to disable squid completely or does it help to disable squidclamav already like in my case? I'm anyway curious that the transparent port of sisters ipfire proxy is 801 (which is an older install) but my fresh setup is using port 3128.
Comment 30 DJ-Melo 2016-10-24 13:36:28 UTC
I have to disable the proxy completly in my case. Only disable btw deinstall clamav and squidclamav didn't work for me. My port is 800 if squid is not transparent andf 3^128 for transparentproxy. if it is standard
Comment 31 DJ-Melo 2016-10-24 18:57:07 UTC
Update: if I squid on green completely off then I get at least 160 mbit the download limitations in the Squid do what you should "unbgrenzt" max 65 mbit where you change that?
Comment 32 DJ-Melo 2016-11-02 08:27:56 UTC
core 107 32 bit testing same problem if squid is on slow. if squid at the green ofd it's not good but ok.
Comment 33 DJ-Melo 2016-11-30 10:19:42 UTC
any hopes to fix this with Core 108?
Comment 34 DJ-Melo 2018-09-25 11:30:47 UTC
with 2.21 Core 123 OK solved i think thx