freenode/#lisp - IRC Chatlog
Search
13:52:22
dim
the code already does (sb-ext:gc :full t) each time it gets rid of a batch, to hint SBCL
16:09:02
oleo
loke: i just used :plot 2d (expression) sin(x) (variable) x (lower bound) -5 (upper bound) 5 to get a plot
16:23:59
oleo
just not sure why output-translations are not defined in quicklisp for the local-projects stuff by default....
19:23:43
dim
the run includes parsing a command language, which returns a lambda form, that is then compiled
19:26:25
scymtym
if you call COMPILE at runtime, some amount of compiler stuff is going to be in the profile (disregarding what PCL might add)
19:26:40
dim
pgloader in that profiled run loaded 121746 rows (36.3 MB) in 2m23.802s, so the compiling shouldn't be leading the profile, that said it's a multi-threaded program, does the profiler knows how to profile multiple threads?
19:28:23
dim
retrying with options (:max-samples 10000 :mode :alloc :report :flat :threads :all :reset t), that should help, maybe
19:30:57
scymtym
dim: if you are adventurous (and your SBCL version is recent enough), you could try https://github.com/scymtym/clim.flamegraph/tree/future to get a more nuanced view
19:33:27
aeth
I notice a lot of things in sprof not directly related to my program. sb-profile seems a lot more useful
19:37:02
dim
though I see calls in the trace that don't seem to belong to the pgloader main thread at all, so I'm quite confused
20:13:46
jeosol
dim: sometimes it pays to leave it for a while and come back, allowing the brain to relax
20:21:38
comborico1611
raynold: Yeah, I'm having a decent day, as well. I think it's because the school children are getting out.
21:47:47
oleo
http://dpaste.com/0K969GG http://dpaste.com/3P713VV http://dpaste.com/2MK678B http://dpaste.com/1F5S302
23:55:53
aeth
I just finished moving nearly everything into with-accessors* and my custom prefixed versions (with-foo-accessors*) in my quest to reduce repetition in Lispy ways. Essentially, it's just with-accessors, but if it's a symbol instead of a list, then it assumes the binding and the accessor are the same name. No more (with-accessors ((width width) (height height)) foo ...)
23:57:21
aeth
I wonder why they didn't do that in the standard. It's a pretty trivial change and I'd assume most uses of with-accessors use the same variable name as the accessor name unless the accessor name is prefixed (and I deal with uniform-for-an-object prefix elimination my own way, with a define-accessor-macro that essentially defines a with-foo-accessors that automatically applies the prefix)