[sage-devel] Re: GMP error handling

Simon King wrote: I am currently implementing sequences of bounded integers (which is useful, e.g., for words over a finite alphabet), and after extensive benchmarks it seems that using GMP's mpz_t to store the sequence (not just one item of the sequence) is rather efficient. But now I wonder: H

[sage-devel] Re: Is this memory leak in polynomial evaluation known?

Nils Bruin wrote: On Sunday, May 25, 2014 5:15:08 AM UTC-7, Simon King wrote: So, it is a tiny amount of memory (~25 byte per round), but I guess it should be fixed anyway. I see a little more memory (~42 bytes). From such a small amount you can already guess no python objects get leak

[sage-devel] GMP error handling

Hi! I am currently implementing sequences of bounded integers (which is useful, e.g., for words over a finite alphabet), and after extensive benchmarks it seems that using GMP's mpz_t to store the sequence (not just one item of the sequence) is rather efficient. But now I wonder: How does GMP han

Re: [sage-devel] Re: trac error, disk full?

Many thanks! On 25 May 2014 17:42, "Keith Clawson" wrote: > I disabled the daemon that was generating massive log files, so the > problem is fixed now. > > -Keith > > > > On Sunday, May 25, 2014 3:01:29 AM UTC-7, Volker Braun wrote: >> >> I've deleted a log file to alleviate the situation. I take

[sage-devel] Re: Is this memory leak in polynomial evaluation known?

Hi Simon! On Sunday, May 25, 2014 5:15:08 AM UTC-7, Simon King wrote: So, it is a tiny amount of memory (~25 byte per round), but I guess it > should be fixed anyway. > I see a little more memory (~42 bytes). From such a small amount you can already guess no python objects get leaked, and ind

[sage-devel] Re: trac error, disk full?

I disabled the daemon that was generating massive log files, so the problem is fixed now. -Keith On Sunday, May 25, 2014 3:01:29 AM UTC-7, Volker Braun wrote: > > I've deleted a log file to alleviate the situation. I take it Keith is in > charge, so I'll send him an email with the details. >

[sage-devel] Re: Is this memory leak in polynomial evaluation known?

Simon King wrote: Hi! On sage-support, the following example was reported (I am giving the figures with Sage 6.2): sage: C. = GF(2)[] sage: f = x^4+x*y^3+z^6 sage: a = f(1,0,0) sage: get_memory_usage() 176.08984375 sage: for i in xrange(100): : a = f(1,0,0) : sage: get_memory_us

[sage-devel] Is this memory leak in polynomial evaluation known?

Hi! On sage-support, the following example was reported (I am giving the figures with Sage 6.2): sage: C. = GF(2)[] sage: f = x^4+x*y^3+z^6 sage: a = f(1,0,0) sage: get_memory_usage() 176.08984375 sage: for i in xrange(100): : a = f(1,0,0) : sage: get_memory_usage() 198.08984

[sage-devel] Re: trac error, disk full?

I've deleted a log file to alleviate the situation. I take it Keith is in charge, so I'll send him an email with the details. On Sunday, May 25, 2014 7:16:08 AM UTC+1, Ralf Stephan wrote: > > Hi, > the "View Tickets" page says: > > *Error: Macro TicketQuery(type=defect,format=count) failed* > >

[sage-devel] Re: trac error, disk full?

Meanwhile trac is practically unusable. Pushing impossible. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to thi