On Mon, Oct 5, 2015 at 5:25 PM, Nikolaus Rath <nr...@trialphaenergy.com> wrote: > Well, it only happens when using matplotlib, so there's got to be some > connection.
this is one good connection indeed. does it happen only on py3k or on py2 as well? >> Additionally, you're testing on python3, python3-matplotlib has only >> been shipped from jessie onward, so your claim that upgrading from >> jessie made its performance poor, it's impossible. > > You mean "upgrading from wheezy", right? Indeed, you're right. I believe I yep > actually updated from some post-wheezy testing snapshot to the jessie > release. > >> I'm afraid you will have to come up with something more related to mpl >> that what's above, as it seems more a shot in the dark. > > Do you have a suggestion what I could try? At the moment I'm seeing even > trivial matplotlib scripts take much longer than they used to, while Python > itself starts as quick as ever. That's why I think it's connected to MPL. you can strace with timing and following the child processes, with -f -ttt (f.e. you might found that that lseek()ing a cached file is not that an issue) at least you can pin point where the time is spent. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
