Moses-support Digest, Vol 105, Issue 51

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Re: decoding-graph-backoff (Hieu Hoang)
2. Re: Performance issues using Moses Server with Moses 3
(Hieu Hoang)
3. OT: Job posting - Assistant Professor in Computational
Linguistics at UNT (Lane Schwartz)


----------------------------------------------------------------------

Message: 1
Date: Thu, 23 Jul 2015 18:36:56 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] decoding-graph-backoff
To: Saumitra Yadav <yadav.saumitra07@gmail.com>, moses-support@mit.edu
Message-ID: <55B0FC08.9010006@gmail.com>
Content-Type: text/plain; charset="windows-1252"

i think you have to swap the phrase tables around. The decoder always
looks at the 1st phrase-table, then backoff to the 2nd if nothing is found

On 22/07/2015 16:59, Saumitra Yadav wrote:
> Sir/Ma'am,
> I'm trying to use multiple phrase tables for translation in Moses
> decoder, with preference to 1st phrase-table, but was getting a
> segmentation fault while loading 1st phrase table, so just switched
> the positions of phrase-tables in moses configuration file and it was
> working , now the table i want to give preference is 2nd in list , can
> i use
>
> [decoding-graph-backoff]
> 1
> 3
> in configuration file for backoff so that moses uses 2nd table and
> uses 1st table only for words it couldn't find in 2nd phrase-table?
>
> Regards,
> Saumitra Yadav
> M.Tech.
> Department Of Computer Science And Technology
> Goa University
>
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support

--
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150723/05305259/attachment-0001.htm

------------------------------

Message: 2
Date: Thu, 23 Jul 2015 18:41:14 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Performance issues using Moses Server
with Moses 3
To: Barry Haddow <bhaddow@staffmail.ed.ac.uk>, Oren
<mooshified@gmail.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID: <55B0FD0A.4090703@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed

run this 1st
cat
/mnt/storage/Common/models/language_models/langmod.5gram.blm/mnt/storage/Common/models/translation_models/moses3_model/train/model/reordering-table.wbe-msd-bidirectional-fe.gz.*
> /dev/null
before running mosesserver. Is there a speedup? If there's speedup, then
it would suggest that IO is a problem

what happens if you use
moses
rather than
mosesserver
? if there's a speedup, then the mosesserver is not able to cope with
the number of connections

On 23/07/2015 18:19, Barry Haddow wrote:
> Hi Oren
>
> You can fit a lot of model in 50G RAM. It's worth looking at the
> compact phrase and reordering models, pruning options, and kenlm
> quantisation, and you might fit the models on one machine.
>
> As to the slowdown, a delay of 20s or so suggests that it's waiting on
> I/O, or perhaps xmlrpc-c is queueing up requests or connections.
>
> cheers - Barry
>
> On 23/07/15 15:06, Oren wrote:
>> More details...
>>
>> Our NFS is mounted at /mnt/storage .
>>
>> The command to run moses server is:
>>
>> /mnt/storage/Common/mosesdecoder3/bin/mosesserver -f
>> /mnt/storage/Common/models/translation_models/moses3_model/mert-work/moses.ini
>> mark-unknown -xml-input -threads 18 exclusive
>>
>> Here is the complete moses.ini (excluding comments):
>>
>>> [input-factors]
>>> 0
>>>
>>> [mapping]
>>> 0 T 0
>>>
>>> [distortion-limit]
>>> 6
>>>
>>> [feature]
>>> UnknownWordPenalty
>>> WordPenalty
>>> PhrasePenalty
>>> PhraseDictionaryMemory name=TranslationModel0 num-features=4
>>> path=/mnt/storage/Common/models/translation_models/moses3_model/train/model/phrase-table.gz
>>> input-factor=0 output-factor=0
>>> LexicalReordering name=LexicalReordering0 num-features=6
>>> type=wbe-msd-bidirectional-fe-allff input-factor=0 output-factor=0
>>> path=/mnt/storage/Common/models/translation_models/moses3_model/train/model/reordering-table.wbe-msd-bidirectional-fe.gz
>>> Distortion
>>> KENLM lazyken=0 name=LM0
>>> path=/mnt/storage/Common/models/language_models/langmod.5gram.blmorder=5
>>>
>>> [threads]
>>> 6
>>>
>>> [weight]
>>>
>>> LexicalReordering0= 0.0268311 -0.0146878 0.0261305 0.0380759
>>> 0.0118265 0.07479
>>> Distortion0= 0.074665
>>> LM0= 0.0972206
>>> WordPenalty0= -0.18469
>>> PhrasePenalty0= -0.212528
>>> TranslationModel0= 0.0184105 0.091358 0.112618 0.0161682
>>> UnknownWordPenalty0= 1
>>
>> On Wednesday, July 22, 2015, Oren <mooshified@gmail.com
>> <mailto:mooshified@gmail.com>> wrote:
>>
>> Yes, we use a lot of RAM in our setup. But the improved response
>> time justifies it.
>>
>> Our language is on a nfs, bit we've been working this way with
>> moses 1 for some time with no problems (ten different machines
>> using the same language model file over nfs). Same for the
>> reordering model. Neither of them is in memory. Raising these
>> models into memory will require raising our already excessive RAM
>> requirements...
>>
>> Thanks again for the help.
>>
>> On Wednesday, July 22, 2015, Barry Haddow
>> <bhaddow@staffmail.ed.ac.uk
>> <javascript:_e(%7B%7D,'cvml','bhaddow@staffmail.ed.ac.uk');>> wrote:
>>
>> Hi Oren
>>
>> I'm not aware of any threading problems with
>> PhraseDictionaryMemory, but not many people use it since it
>> takes up too much memory. Moses command line runs
>> multi-threaded using a thread pool.
>>
>> Is your language model on a local file system? Running it
>> over nfs can be bad. What about your reordering model? Are
>> you using the compact or the memory version?
>>
>> cheers - Barry
>>
>> On 22/07/15 15:09, Oren wrote:
>>> We have no swapping issues. I was asking if the use of
>>> an in-memory translation model might cause multithreading
>>> problems.
>>>
>>>
>>> I'm not sure how to replicate the problem on cmd moses,
>>> since it's purely a multithreading issue. Ca you run cmd
>>> moses multithreaded?
>>>
>>> I can't attach the complete moses.ini because it's on a
>>> separate network... But I copied below the stuff that looked
>>> relevant. I also tried to change the [threads] setting to
>>> 18, with no apparent effect.
>>>
>>> [input-factors]
>>> 0
>>>
>>> [mapping]
>>> 0 T 0
>>>
>>> [distortion-limit]
>>> 6
>>>
>>> [feature]
>>> UnknownWordPenalty
>>> WordPenalty
>>> PhrasePenalty
>>> PhraseDictionaryMemory name=TranslationModel0 num-features=4
>>> path=<path>/phrase-table.gz input-factor=0 output-factor=0
>>> LexicalReordering <parameters>
>>> Distortion
>>> KENLM lazyken=0 name=LM0 path=<path> order=5
>>>
>>> [threads]
>>> 6
>>>
>>> [weight]
>>>
>>> <weight parameters>
>>>
>>> On Tuesday, July 21, 2015, Hieu Hoang <hieuhoang@gmail.com>
>>> wrote:
>>>
>>> is it possible you can make your moses.ini file
>>> available for us to see?
>>>
>>> do you know if the same problem occurs if you use the
>>> command line moses, rather than mosesserver?
>>>
>>>
>>> Hieu Hoang
>>> Researcher
>>> New York University, Abu Dhabi
>>> http://www.hoang.co.uk/hieu
>>>
>>> On 21 July 2015 at 18:07, Barry Haddow
>>> <bhaddow@staffmail.ed.ac.uk> wrote:
>>>
>>>
>>> On 21/07/15 14:51, Oren wrote:
>>>> I am using the in-memory mode, using about 50GB of
>>>> RAM. (No swap issues as far as I can tell.) Could
>>>> that cause issues?
>>>
>>> Yes, swapping would definitely cause issues - was
>>> that your question?
>>>
>>>
>>>>
>>>> I looked at the commit you linked to, but it
>>>> doesn't seem to be something configurable beyond
>>>> the -threads switch. Am I missing something?
>>>
>>> The commit enables you to set the maximum number of
>>> connections to be the same as the maximum number of
>>> threads.
>>>
>>>>
>>>> On Tuesday, July 21, 2015, Barry Haddow
>>>> <bhaddow@staffmail.ed.ac.uk> wrote:
>>>>
>>>> Hi Oren
>>>>
>>>> Does your host have 18 threads available? It
>>>> could also be that xmlrpc-c is limiting the
>>>> number of connections - this can now be configured:
>>>> https://github.com/moses-smt/mosesdecoder/commit/b3baade7f022edbcea2969679a40616683f63523
>>>>
>>>> Slowdowns in Moses are often caused by disk
>>>> access bottlenecks. You can use --minphr-memory
>>>> and --minlexr-memory to make sure that the
>>>> phrase and reordering tables are loaded in to
>>>> memory, rather than being access on-demand.
>>>> Make sure your host has enough RAM and is not
>>>> swapping. As I mentioned before there are
>>>> various ways to make your models smaller
>>>> (http://www.statmt.org/moses/?n=Advanced.RuleTables),
>>>> which can make a big difference to speed
>>>> depending on your setup.
>>>>
>>>> cheers - Barry
>>>>
>>>> On 21/07/15 09:30, Oren wrote:
>>>>> Hi Barry,
>>>>>
>>>>> Thanks for the quick response.
>>>>>
>>>>> I added the switch "-threads 18" to the
>>>>> command to raise moses server. The slowness
>>>>> issue persists but in a different form. Most
>>>>> requests return right away, even under heavy
>>>>> load, but some requests (about 5%) take far
>>>>> longer - about 15-20seconds.
>>>>>
>>>>> Perhaps there are other relevant switches?
>>>>>
>>>>> Thanks again.
>>>>>
>>>>> On Monday, July 20, 2015, Barry Haddow
>>>>> <bhaddow@staffmail.ed.ac.uk> wrote:
>>>>>
>>>>> Hi Oren
>>>>>
>>>>> The threading model is different. In v1,
>>>>> the server created a new thread for every
>>>>> request, v3 uses a thread pool. Try
>>>>> increasing the number of threads.
>>>>>
>>>>> Also, make sure you use the compact phrase
>>>>> table and KenLM as they are normally
>>>>> faster, and pre-pruning your phrase table
>>>>> can help,
>>>>>
>>>>> cheers - Barry
>>>>>
>>>>> On 20/07/15 12:01, Oren wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> We are in the process of migrating from
>>>>>> Moses 1 to Moses 3. We have noticed a
>>>>>> significant slowdown when sending many
>>>>>> requests at once to Moses Server. The
>>>>>> first request will actually finish about
>>>>>> 25% faster that a single request using
>>>>>> Moses 1, but as more requests accumulate
>>>>>> there is a marked slowdown, until
>>>>>> requests take 5 times longer or more.
>>>>>>
>>>>>> Is this a known issue? Is it specific to
>>>>>> Moses Server? What can we do about it?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Oren.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moses-support mailing list
>>>>>> Moses-support@mit.edu
>>>>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moses-support mailing list
>>>>> Moses-support@mit.edu
>>>>> 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
>>> Moses-support@mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>
>>>
>>
>
>
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.

--
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu



------------------------------

Message: 3
Date: Thu, 23 Jul 2015 11:10:05 -0500
From: Lane Schwartz <dowobeha@gmail.com>
Subject: [Moses-support] OT: Job posting - Assistant Professor in
Computational Linguistics at UNT
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CABv3vZnwKc4OiUZWx2hKkUiPLkxLcj5NP-mdDO13CjbtEueEFQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

*Assistant Professor? Computational Linguistics *

*University of North Texas *

*Linguistics Program, College of Information*



The Linguistics Program at the University of North Texas invites
applications for the position of Assistant Professor in Linguistics with a
specialization in Computational Linguistics beginning fall 2015 or soon
thereafter. While the area of computational linguistics is open, we seek
candidates who are active researchers in a core linguistics area. Desirable
qualifications include a strong background in computational techniques for
analyzing text and discourse, including but not limited to, semantic
models, NLP techniques, machine learning, and automated scoring. Evidence
of an active research agenda and a strong commitment to innovative teaching
in an interdisciplinary context is required for consideration.



The recent move of Linguistics to the College of Information has positioned
the Linguistics Program in a collaborative environment for developing
cutting-edge curricula and facilitating research in computational and
quantitative methods in linguistics. The successful candidate will have the
opportunity to build a program from the ground up bringing together
Linguistics with the research strengths in the Departments of Computer
Science and Engineering, Library and Information Sciences, and Learning
Technologies.



UNT offers 99 bachelor?s, 83 master?s, and 36 doctoral degree programs,
many nationally and internationally recognized. The Linguistics program at
UNT offers a BA in Linguistics, an MA in Linguistics, MA in ESL, and a
Graduate Academic Certificate in TESOL. Students in the Interdisciplinary
Information Science (IIS) Ph.D. program may also opt to specialize in
linguistics. Additional information about degrees, courses, and faculty can
be found at linguistics.unt.edu.



The University of North Texas System is firmly committed to equal
opportunity and does not permit ? and takes actions to prevent ?
discrimination, harassment (including sexual violence), and retaliation on
the basis of race, color, religion, national origin, sex, sexual
orientation, gender identity or expression, age, disability, family status,
genetic information, citizenship or veteran status in its application and
admission processes, educational programs and activities, facilities, and
employment practices. The University of North Texas System immediately
investigates and takes remedial action when appropriate. The University of
North Texas System also takes actions to prevent retaliation against
individuals who oppose a discriminatory practice, file a charge, or
testify, assist or participate in an investigative proceeding or hearing.



A PhD in Linguistics, Computer Science, Cognitive Science or a related
field with a strong background in computational linguistics / natural
language processing is required by the time of the appointment. Please
submit all application materials electronically at
facultyjobs.unt.edu/applicants/Central?quickFind=52219

Review of applications will begin immediately and will continue until the
search is closed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150723/995de43f/attachment.htm

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 105, Issue 51
**********************************************

Tweet