Hi,
In mgiza, I noticed that the HMM model is a lot slower with 8 threads
than with 4 threads. It becomes a lot worse for 16 threads or more.
Multi-threading is the main feature of mgiza, so this kind of defies the
whole sense of the thing to the extend that I would say mgiza is broken.
Haven't
Marcin Junczys-Dowmunt junczys@... writes:
will try to have a look what is going on there (I dread the code), but if
anyone has some ideas, the same experience or wants to help that would be
most welcome. It seems Model 1 is fine, and speed improves with a greater
number of threads, but the
Hi Rico,
there is more going on than that. I just disabled all those locks for
testing and nothing changes (funnily it's not even crashing). I will try
to have a look. Rewriting everything so each thread get's
thread-specific datastructures might be more than I am ready to do
though. On the
Hi,
would anyone object to making mgiza depend on -std=c++11? I checked, it
compiles and works. Since I am contemplating to bring some order into
the threading issues, I would appreciate to get rid of pthread,
boost::thread and make use of thread, mutex and stuff. Also it seems
mutex is
i don't mind. I've made a branch
PRE_CPP11
just in case nothing works and you change your mind
On 23 December 2014 at 04:13, Marcin Junczys-Dowmunt junc...@amu.edu.pl
wrote:
Hi,
would anyone object to making mgiza depend on -std=c++11? I checked, it
compiles and works. Since I am
