[elephant-devel] Serializer compatibility

Ian Eslick eslick at media.mit.edu
Fri Feb 27 16:02:24 UTC 2009

On Feb 27, 2009, at 3:56 AM, Leslie P. Polzer wrote:

>> 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.

True, although we do have an MT stress test which also tests the  

Sometimes errors in the serializer stem from:
1) A missing schema in the schema table
2) A missing package for a symbol that was defined earlier

I fixed a few bugs in schema management in the past three months.   
It's possible you have stale state left over from when those bugs were  
present.  When I have some time perhaps I can write some code to do a  
consistency check for the whole DB.


>> 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 at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel

More information about the elephant-devel mailing list