Moses-support Digest, Vol 92, Issue 46

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: Performance issues in 2.1.1 (Mike Ladwig)
2. Re: PhraseDictionaryFuzzyMatch (Hieu Hoang)
3. Re: Performance issues in 2.1.1 (Barry Haddow)


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

Message: 1
Date: Thu, 26 Jun 2014 09:26:43 -0400
From: Mike Ladwig <mdladwig@gmail.com>
Subject: Re: [Moses-support] Performance issues in 2.1.1
To: Hieu Hoang <Hieu.Hoang@ed.ac.uk>, moses-support@mit.edu
Message-ID:
<CAB3VaD2PObPobSvihv1KYQSdPXtqUEObG86ZUaH7_DudZC9Sug@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

The results I posted were from experiments with moses-cmd and not from my
thread pool version of mosesserver, although the results were similar.

I looked the in the archives, and can find no explanation for the new cache
approach (global to per-thread). What use case is improved with this
approach?


On Thu, Jun 26, 2014 at 9:19 AM, Hieu Hoang <Hieu.Hoang@ed.ac.uk> wrote:

> Is the performance ok with the command line version? Can you push your
> thread pool changes to a new branch.
>
> I'll take a look at it when I get the chance
>
>
> On 25 June 2014 16:25, Mike Ladwig <mdladwig@gmail.com> wrote:
>
>> I'm trying to move from the moses 1.x release to 2.x, but have
>> encountered large performance issues. On my workstation (Scientific Linux
>> 6.5), using the same spa-eng data to create two systems I get performance
>> roughly 3x slower on release 2.1.1.
>>
>> I started by comparing moseserver between the 1.x and 2.x releases.
>> After discovering the "single phrase cache per thread" issue, I rewrote
>> mosesserver using a thread pool but only got a 10-20% improvement.
>>
>> Thinking I might not really have fixed mosesserver, I tried comparing
>> unmodified moses-cmd speed between releases. The values are in words per
>> minute for a 2000 line, 48k word file.
>>
>> 1T 4T 8T
>> Rel 1: 4850 16492 19500
>> Rel 2: 1742 5324 6559
>>
>> Any suggestions?
>>
>> Regards,
>> mike.
>>
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>>
>
>
> --
> Hieu Hoang
> Research Associate
> University of Edinburgh
> http://www.hoang.co.uk/hieu
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20140626/92ad5077/attachment-0001.htm

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

Message: 2
Date: Thu, 26 Jun 2014 09:34:40 -0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] PhraseDictionaryFuzzyMatch
To: Jon Olds <joft_uk@yahoo.co.uk>, moses-support
<moses-support@mit.edu>
Message-ID: <53AC2170.7020104@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

ah, I forgot to register the feature. Fixed, please git pull and recompile:
https://github.com/moses-smt/mosesdecoder/commit/dba4caa7c0de9d6b364653a05f23cef7c2ed0b7f

There's some documentation for it here:
http://www.statmt.org/moses/?n=Moses.AdvancedFeatures#ntoc55
Note - it can only be used with the hierarchical/syntax model, not
phrase-based. I think it can be used with the server.

It was integrated into Moses a few years ago but no-one seems to have
used it. If you have any problems, please let us know

On 26/06/14 07:48, Jon Olds wrote:
> Hi,
>
> I would like to test out the PhraseDictionaryFuzzyMatch feature in Moses.
>
> Do I need to do something special when compiling Moses, as this feature
> does not appear to be available in moses_chart as things stand? (see
> output of moses_chart with no arguments below).
>
> Also, can it be used with Mosesserver (in theory)?
>
> Cheers,
>
> Jon
>
>
> Available feature functions:
> KENLM IRSTLM SkeletonStatelessFF SyntaxRHS NieceTerminal
> MaxSpanFreeNonTermSource RuleScope SetSourcePhrase ReferenceComparison
> HyperParameterAsWeight SoftMatchingFeature CoveredReferenceFeature
> ConstrainedDecoding OpSequenceModel UnknownWordPenalty ExternalFeature
> SkeletonStatefulFF PhraseDictionaryALSuffixArray
> PhraseDictionaryMultiModelCounts PhraseDictionaryMultiModel
> PhraseDictionaryMemory PhraseDictionaryDynSuffixArray SpanLength
> CountNonTerms InputFeature PhrasePenalty WordPenalty Distortion
> Generation TargetNgramFeature TreeStructureFeature TargetBigramFeature
> PhraseLengthFeature LexicalReordering SourceGHKMTreeInputMatchFeature
> PhraseBoundaryFeature BleuScoreFeature SkeletonLM ControlRecombination
> TargetWordInsertionFeature WordTranslationFeature
> PhraseDictionaryTransliteration SourceWordDeletionFeature SkeletonPT
> PhraseDictionaryBinary GlobalLexicalModel PhraseDictionaryOnDisk
> PhrasePairFeature PhraseDictionaryScope3
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>



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

Message: 3
Date: Thu, 26 Jun 2014 14:43:49 +0100
From: Barry Haddow <bhaddow@staffmail.ed.ac.uk>
Subject: Re: [Moses-support] Performance issues in 2.1.1
To: Mike Ladwig <mdladwig@gmail.com>, Hieu Hoang
<Hieu.Hoang@ed.ac.uk>, moses-support@mit.edu
Message-ID: <53AC2395.9000603@staffmail.ed.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Mike

Using a cache per-thread removes the need for locking on the cache, so
should be faster. The negative effect on mosesserver was unexpected, but
if you'd be able to make your threadpool changes available then that
would be really helpful.

As to the general performance problems, our own tests
(http://www.statmt.org/mosescore/uploads/Internal/D1.3_Moses_v2_Release_Notes.pdf)
showed v2.1.1 to be slightly faster than v1, however we did not test all
possible configurations. If you could tell us a bit more about your
setup then it would help us find out what the problem is.

cheers - Barry

On 26/06/14 14:26, Mike Ladwig wrote:
> The results I posted were from experiments with moses-cmd and not from
> my thread pool version of mosesserver, although the results were similar.
>
> I looked the in the archives, and can find no explanation for the new
> cache approach (global to per-thread). What use case is improved with
> this approach?
>
>
> On Thu, Jun 26, 2014 at 9:19 AM, Hieu Hoang <Hieu.Hoang@ed.ac.uk
> <mailto:Hieu.Hoang@ed.ac.uk>> wrote:
>
> Is the performance ok with the command line version? Can you push
> your thread pool changes to a new branch.
>
> I'll take a look at it when I get the chance
>
>
> On 25 June 2014 16:25, Mike Ladwig <mdladwig@gmail.com
> <mailto:mdladwig@gmail.com>> wrote:
>
> I'm trying to move from the moses 1.x release to 2.x, but have
> encountered large performance issues. On my workstation
> (Scientific Linux 6.5), using the same spa-eng data to create
> two systems I get performance roughly 3x slower on release 2.1.1.
>
> I started by comparing moseserver between the 1.x and 2.x
> releases. After discovering the "single phrase cache per
> thread" issue, I rewrote mosesserver using a thread pool but
> only got a 10-20% improvement.
>
> Thinking I might not really have fixed mosesserver, I tried
> comparing unmodified moses-cmd speed between releases. The
> values are in words per minute for a 2000 line, 48k word file.
>
> 1T 4T 8T
> Rel 1: 4850 16492 19500
> Rel 2: 1742 5324 6559
>
> Any suggestions?
>
> Regards,
> mike.
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
>
> --
> Hieu Hoang
> Research Associate
> University of Edinburgh
> http://www.hoang.co.uk/hieu
>
>
>
>
> _______________________________________________
> 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


End of Moses-support Digest, Vol 92, Issue 46
*********************************************

Tweet