Hi,
Andy Wingo skribis:
> On Tue 24 Apr 2012 18:31, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> I spent some time poking at vlists and ended up squeezing out a little
>>> bit of performance.
>>
>> Any figures?
>
> Well, last time I checked, with the patch compiling pe
Hi,
i hope that I do not bore you with continuing talking about guile-log.
But one of the things brought up by Mark, and rightly so, are that having
the fundaments
of logic programming based on a stack compared to assq lists or similar more
scalable functional data structures makes it complicated
Heya Ludo,
On Tue 24 Apr 2012 18:31, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> I spent some time poking at vlists and ended up squeezing out a little
>> bit of performance.
>
> Any figures?
Well, last time I checked, with the patch compiling peval.scm was 2.10
seconds, c
Heya Neil,
I pushed a change to the format of the text logged to the console when
you do a ./benchmark-guile. It seems that this affected your
benchmarking bot. I was hoping that this would not be the case, because
the benchmark suite also writes a log to `guile-benchmark.log', and I
tried to av
Noah Lavine skribis:
> Yes, you're right. Those tests showed me how to get a stack. I pushed
> the fix with two new test cases, and then cleaned up the stack-test
> code a bit.
Excellent, thank you!
Ludo’.
Hi!
Andy Wingo skribis:
> I went ahead and pushed this branch to stable-2.0. We can roll it out
> again if it causes problems.
Cool, thanks!
> I spent some time poking at vlists and ended up squeezing out a little
> bit of performance.
Any figures?
> I ended up allocating the hash table dat
On Fri, Mar 16, 2012 at 3:34 AM, Nala Ginrut wrote:
> I didn't saw any error with your information, and I think it's normal. The
> *.go compiling is very slow even if you have a good machine. So be patient.
Yes compiling these files is quite expensive and I have found that it
can run into resourc
Hi!
I went ahead and pushed this branch to stable-2.0. We can roll it out
again if it causes problems.
I spent some time poking at vlists and ended up squeezing out a little
bit of performance. I ended up allocating the hash table data inline to
the content vector, after some care looking at wh
