Re: Is it a bad sign...

Kenny <kentilton@xxxxxxxxx> writes:

OK, 6.5m symbols. That's a lot, right?

That's a lot. But... I just interned 11.6m symbols into package foobar:

(with-open-file (f "/usr/share/dict/words")
(loop for word = (read-line f nil nil)
while word
do (loop for i below 50
do (intern (format nil "~a~a" (string-upcase word) i) :foobar))))

That took a few minutes, mostly because I forgot to quit the memory
hogs Safari and iPhoto before I told 64 bit LW for mac to do this (my
linux box has 4GB RAM, I tend to forget that 2GB on my MacBook is not
that much for experiments like this, and swapping against a 5400rpm
laptop disk is no fun).

But once it was done, apropos is fast:

FOOBAR 56 > (time (apropos :giraffe :foobar))
Timing the evaluation of (APROPOS :GIRAFFE :FOOBAR)
GIRAFFE8
[stuff deleted]
GIRAFFESQUE44
GIRAFFESQUE42
User time = 0.912
System time = 0.009
Elapsed time = 1.127
Allocation = 78752 bytes
10 Page faults

FOOBAR 57 >

Is AMD any different than Intel, or shouls I save $150?

It's definitely different, but it depends on operating system and
lisp implementation, I guess.

For 64 bit LispWorks on linux, we get much better results with Core 2
than with Opteron - with 32 bit linux/lisp, Opteron and Core 2 are not
that much different. And depending on your application, 64 bit can give
you advantages even for applications with small memory footprint.
--
(espen)
.

Relevant Pages

  • Re: Is it a bad sign...
    ... I just interned 11.6m symbols into package foobar: ... (loop for word = (read-line f nil nil) ... do (loop for i below 50 ... than with Opteron - with 32 bit linux/lisp, Opteron and Core 2 are not ...
    (comp.lang.lisp)
  • Re: Running methods in parallel
    ... it must use some loop statement. ... Each call to run_one_slice performs one foobar activity. ... If you start with a good architecture, and measure it, you will know if its performance is adequate, or if it needs more help. ... And threads work best with event-driven architectures, so adding the thread last is always better than adding it first. ...
    (comp.lang.ruby)
  • Re: Loop optimization
    ... haroon wrote ... > I have two versions of a loop. ... Randy Howard (2reply remove FOOBAR) ...
    (comp.lang.c)
  • Re: debug my awful code (Timex 80 column display driver)
    ... <main code of loop> ... macro foobar ...
    (comp.sys.sinclair)