|
I forgot to add that I am using
cube-pruning, with stack decoding moses uses pretty much all the
available cores in one process. Cube-pruning seems to be so fast
that lockage becomes an issue.
W dniu 15.01.2014 09:40, Marcin Junczys-Dowmunt pisze:
From my experience more than 16
threads per moses process causes performance to decrease. I have
64 cores, too. I use GNU parallel to get around this.
cat input.txt | parallel --pipe -k -j 4 ./mosesdecoder/bin/moses
-f moses.ini -threads 16 > out.txt
This launches 4 moses processes a 16 threads and translates
blocks of roughly 1MB per processes. You only see output after a
block has been translated. You can set block size by using for
instance --block 10K , then it will create and kill the moses
processes much faster and output intermediate results.
You can get GNU parallel from http://ftp.gnu.org/gnu/parallel/parallel-latest.tar.bz2
.
Make sure to delete /etc/parallel/config after installation.
Best,
Marcin
W dniu 15.01.2014 08:24, Hansung Cho pisze:
hello.
To change the option "-threads 64" then monitoring at
server CPUs status.
but, result is the same..
Try the other way?
Attach the CPUs status picture
thank you
Hansung Cho
_______________________________________________
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
|
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support