Re: [sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Dan Drake
On Fri, 19 Nov 2010 at 02:12PM +, Willem Jan Palenstijn wrote: > Could you try to download, compile and run a small test program on a > problematic machine? It times how fast a pseudo-terminal responds, which might > be the problem judging by a few quick tests I ran. > > wget http://www.usecod

[sage-devel] Pexpect, _synchronize and clear

2010-11-19 Thread Simon King
Hi all, but in particular hi Willem-Jan and William! I think the thread about pexpect slowness is long enough. So, I factor one idea out. Assume that the garbage collector has been active on SingularElements. Hence, there are some variables in Singular marked for deletion. Now, if singular.eval

[sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Simon King
On 19 Nov., 18:39, Simon King wrote: > But I don't know where the third call happens when creating a > SingularElement (recall: _synchronize() is responsible for one third, > the rest of eval(...) for another third of the overhead of creating a > SingularElement). Perhaps worth to analyze. Got it

[sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Simon King
Hi Willem! On 19 Nov., 15:12, Willem Jan Palenstijn wrote: > Could you try to download, compile and run a small test program on a > problematic machine? It times how fast a pseudo-terminal responds, which might > be the problem judging by a few quick tests I ran. > > wget http://www.usecode.org/m

Re: [sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread David Kirkby
On 19 November 2010 15:11, Dima Pasechnik wrote: > > > On Nov 19, 10:12 pm, Willem Jan Palenstijn wrote: >> On Thu, Nov 18, 2010 at 11:47:38PM -0800, Simon King wrote: >> > On 19 Nov., 07:28, Simon King wrote: >> > > So, now the question is what all the machines have in common. I notice >> > > t

[sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Dima Pasechnik
On Nov 19, 10:12 pm, Willem Jan Palenstijn wrote: > On Thu, Nov 18, 2010 at 11:47:38PM -0800, Simon King wrote: > > On 19 Nov., 07:28, Simon King wrote: > > > So, now the question is what all the machines have in common. I notice > > > that it is Ubuntu in many (or all?) cases. One of the machi

Re: [sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Willem Jan Palenstijn
On Thu, Nov 18, 2010 at 11:47:38PM -0800, Simon King wrote: > On 19 Nov., 07:28, Simon King wrote: > > So, now the question is what all the machines have in common. I notice > > that it is Ubuntu in many (or all?) cases. One of the machines at my > > university used to *not* show the big overhead

[sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Simon King
Hi Dan! On 19 Nov., 12:33, Dan Drake wrote: > For what it's worth, I ran your tests on my Macbook. It's an Intel > Macbook from 2006 or 2007, running OS X 10.5 and Sage 4.5. Thank you! Meanwhile I contacted Noah (the pexpect developer). Let's see what he thinks about it. Best regards, Simon -

Re: [sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize

2010-11-19 Thread Dan Drake
On Thu, 18 Nov 2010 at 10:28PM -0800, Simon King wrote: > So, now the question is what all the machines have in common. I notice > that it is Ubuntu in many (or all?) cases. One of the machines at my > university used to *not* show the big overhead when it was running > Scientific Linux. Now it is

[sage-devel] leave of absence

2010-11-19 Thread François Bissey
Hi all, I have a new job starting on the 1st of December which involves relocation. >From the North Island of New Zealand to the South Island. So I will be out of action from sometimes next week until probably the end of December. So no pinging me for review or for particular bugs on trac. I may m