Hi Sara > I noticed that it says on the Moses webpage that multi-threaded Moses > for lattices is not tested. Does anyone know why there is this problem, > and have an idea of where to start looking to try and fix this?
I think I wrote this because there seemed to be some extra caching for lattices in the InitializeForInput methods. Actually it looks like it's for ConfusionNets. If it's running really slow with threads, then maybe there's some heavy lock contention? In the translation option cache perhaps? You could try switching this off and see if it improves things. If you grep for mutex in the code then you should see all the places where locks are used. Profiling may help (see valgrind) or just periodically attaching a debugger to see where the threads are waiting. > > Also, I trained my translation model using memscore, and it produced an > old phrasetable format: > > ! ! ! ) ||| !|SENT !|SENT !|SENT )|) ||| (0) (1) (2) (3) ||| (0) (1) (2) > (3) ||| 0.666667 0.532303 0.666667 0.000387809 2.718 > Feel free to fix this ... it looks as though no-one updated memscore when the table format changed, cheers - Barry -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
