Hi Marcos This should be fixed.
The problem was that mosesserver used a thread per connection, and some of the caches were on a per thread basis, so mosesserver effectively did not have caching. I updated mosesserver so that it uses a fixed size thread pool for translation, the same as command-line moses, cheers - Barry On 06/02/15 12:31, Marcos Fernandez wrote: > Hi, > > great news! > > But, has it been any changes in Moses Server related to the way in which it > uses the translation caches?. Some months ago we discussed about it, and > Barry (I think it was him) stated that the new global cache mechanism > (instead of the previous per-thread caches), is useful for stand-alone moses > but it has a negative impact over Moses Server because new requests are > attended in new threads whose caches are empty when they are created. > > Thanks, > Marcos > > > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > -- 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
