1:38:34Bikei don't understand the emphasis on joining
1:38:42Bikejoining just means you wait for a thread to be done. the actual task is the compiling
1:57:50drmeisterI think that's what the problem is. If you run a tight loop that generates lots of threads and joins them I don't think the overhead is that high.
2:05:55kpoeck_ Before joining i took get-internal ...
2:08:35drmeisterThe contention that I'm seeing is a little hard to demonstrate. If you profile compile-file-parallel you will see that the top thread that compiles the ASTs spends a lot of time in llvm.
2:09:30drmeisterSo then I tell it to use the interpreter rather than the compiler when generating ASTs.
2:16:30drmeisterSo THEN I tell it to not launch threads to compile the ASTs to native code and then the AST generation is 10x faster
2:17:47drmeisterBike: I'm still having trouble saving CLOS objects with the printer in a readable way- what did I need to do to add that for an object?
2:17:55drmeisterImplement print-object and make-load-form?
2:18:08Bikeprint-object is for the printer. make-load-form is for compile-file.
2:36:14drmeisterBut if I want to print the class of an object and the slots in a way that I can recreate the object when I load the file...