> LPP> I spawned a thread that does some heavy slot access. So maybe > LPP> the serializer isn't entirely multi-thread or multi-process safe > LPP> yet? > > maybe. there were some issues with it (trivial ones), who knows, > maybe we've overlooked something.
We should probably consider adding an MT test suite for the serializer. > if you have a multi-core system and value stability over performance, i > strongly > recommend binding you lisp process to a single core (via taskset in Linux, > for example). > this way multithreading-related issues will have much less chances to > happen. No choice in a web server environment, I guess. :) Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/ _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
