make -j sets the number of processes to compile Moses. It impacts the speed with which Moses compiles. It has no impact on the binary produced and, therefore, no impact on training or decoding time. There is no maximum but, as some files depend on others, only so many files can be compiled simultaneously. Also, it will eventually slow down due to context switches / thrashing.
-threads is the number of threads to use for decoding. This is probably the one you care about more as it impacts decoding speed. On 01/03/11 10:23, [email protected] wrote: > According to the moses_steps page, the -j X option sets the "number of > simultaneous tasks is a speedier option for machines with multiple > processors." > > Moses decoder also supports an option -threads x to set the number of > parallel threads during decoding (assuming the language model supports > multi-threading). > > I saw somewhere that setting the -j option to more than the number of > cores can be beneficial with a large number of cores. I'm building a > training/decoding machine with 12 cores (two sockets with 6 cores each) > and 48 GB RAM. Is there any advantage to compiling moses with -j 13 or > 14? Is there a maximum? What is the relationship between the -j compile > option and the -threads runtime option? > > Thanks, > Tom > > > > > > > > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
