IEP console very slow on Arch Linux

[marek...@gmail.com]

After some recent system update (python 3.5.1), IEP console has become really slow. It takes about 4 seconds to process any command (e.g. import numpy). Has anyone else experienced this problem? Any idea what could be causing it?

Thanks!
Marek

[Almar Klein]

I have no idea. Have you tried the obvious uninstall + reinstall?

--
You received this message because you are subscribed to the Google Groups "Interactive Editor for Python" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iep_+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

 

[sg...@cinghiale.de]

I can confirm these problems on a recent Arch Linux installation. Python 3.5.1, IPython 4.1.1. E.g. a '!ls -l' in a command shell takes several seconds, and the result is displayed slowly in small chunks. This is a new behavior, which didn't show up two weeks ago. Uninstall + reinstall didn't help. It doesn't seem to be an IEP problem - but if I can help with some further investigation, please let me know.

Georg

[Almar Klein]

You could try running python in the terminal to see if its slow there too. Then try IPython in the terminal perhaps. If it works slow there as well, the problem is with your system Python. Otherwise it might well be IEP.

 

In the latter case ... are you using the IEP binaries, or have you installed IEP “from scratch”, i.e. with your system Python and PyQt4? You could try both approaches.

 

- Almar

[sg...@cinghiale.de]

Python and IPython in a terminal are OK, the installation from AUR repository as well as the binary installation from IEP site both show the slow command shell.

Georg

[Marek Petrik]

It is the same for me, both Python 3.5.1 and IPython work fine in the terminal. They are slow for the binary IEP installation, as well as for an installation from source. Both Python and IPython work fine in Spyder.

Marek

[Almar Klein]

Strange, what GUI integration are you using?

 

 

 

From: Marek Petrik
Sent: 16 February 2016 00:29
To: sg...@cinghiale.de
Cc: Interactive Editor for Python
Subject: Re: [IEP] IEP console very slow on Arch Linux

 

It is the same for me, both Python 3.5.1 and IPython work fine in the terminal. They are slow for the binary IEP installation, as well as for an installation from source. Both Python and IPython work fine in Spyder.

Marek

--

[Hector Martinez-Seara]

Hi

I'm the maintainer of iep in archlinux and a frequent user.

A they mention above for some time console in iep is extremely

slow in archlinux. I have tried to figure out why, but so far no luck.

The environment seem not to be the problem as it is the

same whether I use python2 or python 3 for the console. The respectives ipython

integration also are affected. Also pyqt and pyside are affected.

All this programs are fine when used outside iep. I have even tried

the python install done by conda after a clean install without better

luck. I have tried to downgrade few of the packages to try to find the

problem but I cannot go below python 3.5 without having to uninstall

great part of my system.

I will keep investigating but so far nothing and as it is now is not really

usable. Thanks

Hector 

--

Hector Martínez-Seara Monné
mail: hse...@gmail.com
Tel: +420775096757

Tel: +358442709253

[Almar Klein]

What about an older version of IEP?

[Hector Martinez-Seara]

Hi,

I checked this as you request. Iep 3.6 and 3.4 provide now the same slowness

in the console at the moment. Also, I have uninstalled python-pyqt4 bindings to be sure

iep uses pyside. But the result is the same.

Any other idea?

Hector

[Almar Klein]

Thanks Hector,

 

Pfff, so its not related to anything new that we added. This reminds me a bit on the appnap feature that was introduced for OSX at some point. There was not such a feature added to Arch Linux, I presume (a feature that puts idle processes in a sort of sleep mode)?

 

- Almar

[Hector Martinez-Seara]

Hi,

after some research, I got clear clues that the problem is the the linux kernel.
When I use the latest, 4.4.1-2-ARCH at this moment, then all this slowness

happens. Instead when I use the lts kernel all the problems suddenly disappear,

and everything goes back to normal.

Curiously, when iep is malfunctioning the following problems gets recorded in the systemd

journal system:

kernel: TCP: request_sock_TCP: Possible SYN flooding on port 54847. Sending cookies.  Check SNMP counters.
If I do not recall badly the communication between iep windows was TCP using yoton.

Every time, I restart the python console I get again the same message. I guess this is relevant.

Still this does not provide a solution, it just points to the source of the problem.

I hope it helps,

Hector

[Almar Klein]

Great that we have something to go on! Reading https://en.wikipedia.org/wiki/SYN_flood, it looks like the kernel thinks there is an attack, and supposedly throttles the TCP connection or something. Not sure why the kernel thinks we’re doing that, because AFAICT we don’t interrupt a TCP handshake or anything. Maybe its related to how we try to connect to a free port? https://github.com/pyzo/pyzo/blob/master/pyzo/yoton/connection_tcp.py#L166-L176

[hervedu...@gmail.com]

same problem on linux mint kernel 4.4.3. No problem with kernel 3.19

[Almar Klein]

Oh dear,

 

I bet it’s on Ubuntu too then. That’s bad...

 

Regards,

  Almar

 

 

 

From: hervedu...@gmail.com
Sent: 28 February 2016 21:28
To: Interactive Editor for Python
Cc: marek...@gmail.com

--

[AnthonyM]

I am having this problem now on Fedora 23. Any updates since February?

[Almar Klein]

I pan to find/make time to work on this ASAP. Hopefully next week.

 

 

 

From: AnthonyM
Sent: 14 March 2016 18:50
To: Interactive Editor for Python
Cc: marek...@gmail.com
Subject: [IEP] Re: IEP console very slow on Arch Linux

 

I am having this problem now on Fedora 23. Any updates since February?

--

[Almar Klein]

This is now fixed. All should work fine in the next release. To fix locally, edit the yoton.connection_tcp.py and change listen(0) to listen(1). Also see https://github.com/pyzo/pyzo/issues/381

 

Thanks for the reports, all.

[Marek Petrik]

Thanks! That fixed the problem for me.