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: Moses-support Digest, Vol 122, Issue 29 (Tomasz Gawryl)
2. Re: Moses-support Digest, Vol 122, Issue 29 (Shubham Khandelwal)
3. Re: Moses-support Digest, Vol 122, Issue 29 (Mathias M?ller)
----------------------------------------------------------------------
Message: 1
Date: Fri, 16 Dec 2016 08:50:26 +0100
From: "Tomasz Gawryl" <tomasz.gawryl@skrivanek.pl>
Subject: Re: [Moses-support] Moses-support Digest, Vol 122, Issue 29
To: <moses-support@mit.edu>
Message-ID: <044901d25771$103c1660$30b44320$@skrivanek.pl>
Content-Type: text/plain; charset="us-ascii"
Hi,
If you want to speed up decoding time maybe you should consider changing
searching algorithm. I'm also using compact phrase tables and after some
test I realised that cube pruning gives almost exactly the same quality but
is much faster. For example you can add something like this to your config
file:
# Cube Pruning
[search-algorithm]
1
[cube-pruning-pop-limit]
1000
[stack]
50
If your model allows you may also try moses2 binary which is faster than
original.
Regards,
Thomas
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Dec 2016 19:12:01 +0530
From: Shubham Khandelwal <skhlnmiit@gmail.com>
Subject: Re: [Moses-support] Regarding Decoding Time
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAHweNTvYeALYrAfJDgDiH51t5_AHSPRV0KwLCABC2td27yoHmA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
Currently, I am using phrase-table.minphr , reordering-table.minlexr and
language model (total size of these 3 are 6 GB). Now, I tried to decode on
two different machines (8 core-16GB RAM *&* 4 core-40GB RAM) using them.
So, During decoding of around 500 words, it took 90 seconds and 100 seconds
respectively on those machines. I am already using compact phrase and
reordering table representations for faster decoding. Is there any other way
to reduce this decoding time.
Also, In Moses, Do we have distributed way of decoding on multiple machines
?
Looking forward for your response.
------------------------------
Message: 2
Date: Fri, 16 Dec 2016 15:02:55 +0530
From: Shubham Khandelwal <skhlnmiit@gmail.com>
Subject: Re: [Moses-support] Moses-support Digest, Vol 122, Issue 29
To: Tomasz Gawryl <tomasz.gawryl@skrivanek.pl>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAHweNTt=GJcaizcmPeABWeG6aGv6D5N9Sf94QsrQf+NAwCXCNw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hey Thomas,
Thanks for your reply.
Using Cube Pruning, the speed is littile bit high, but not that much. I
will try to play with these parameters.
I have binary moses2 which supports it aswell but it is taking more time to
than moses. Can you please send/share somewhere your binary moses2 file if
possible ?
Also, I do not wish to run this command ( ~/mosesdecoder/bin/moses
-f moses.ini -threads all) every time for every input. Is there any way in
Moses by which all models will load in memory for forever and I can just
pass a input and get output in real time without using this command again
and again.
Looking forward for your response.
Thanks again.
On Fri, Dec 16, 2016 at 1:20 PM, Tomasz Gawryl <tomasz.gawryl@skrivanek.pl>
wrote:
> Hi,
> If you want to speed up decoding time maybe you should consider changing
> searching algorithm. I'm also using compact phrase tables and after some
> test I realised that cube pruning gives almost exactly the same quality but
> is much faster. For example you can add something like this to your config
> file:
>
> # Cube Pruning
> [search-algorithm]
> 1
> [cube-pruning-pop-limit]
> 1000
> [stack]
> 50
>
> If your model allows you may also try moses2 binary which is faster than
> original.
>
> Regards,
> Thomas
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 15 Dec 2016 19:12:01 +0530
> From: Shubham Khandelwal <skhlnmiit@gmail.com>
> Subject: Re: [Moses-support] Regarding Decoding Time
> To: Hieu Hoang <hieuhoang@gmail.com>
> Cc: moses-support <moses-support@mit.edu>
> Message-ID:
> <CAHweNTvYeALYrAfJDgDiH51t5_AHSPRV0KwLCABC2td27yoHmA@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> Currently, I am using phrase-table.minphr , reordering-table.minlexr and
> language model (total size of these 3 are 6 GB). Now, I tried to decode on
> two different machines (8 core-16GB RAM *&* 4 core-40GB RAM) using them.
> So, During decoding of around 500 words, it took 90 seconds and 100 seconds
> respectively on those machines. I am already using compact phrase and
> reordering table representations for faster decoding. Is there any other
> way
> to reduce this decoding time.
>
> Also, In Moses, Do we have distributed way of decoding on multiple machines
> ?
>
> Looking forward for your response.
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
--
Yours Sincerely,
Shubham Khandelwal
Masters in Informatics (M2-MoSIG),
University Joseph Fourier-Grenoble INP,
Grenoble, France
Webpage: https://sites.google.com/site/skhandelwl21/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20161216/65ab78a4/attachment-0001.html
------------------------------
Message: 3
Date: Fri, 16 Dec 2016 11:59:50 +0100
From: Mathias M?ller <mathias.mueller@uzh.ch>
Subject: Re: [Moses-support] Moses-support Digest, Vol 122, Issue 29
To: Shubham Khandelwal <skhlnmiit@gmail.com>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAF2XUm1f74XYPEB0erQPo_+VuKGorGDz4N71wtSCvQGrWm6VGA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Shubham
You could start Moses in server mode:
$ moses -f /path/to/moses.ini --server --server-port 12345 --server-log
/path/to/log
This will load the models, keep them in memory and the server will wait for
client requests and serve them until you terminate the process. Translating
is a bit different in this case, you have to send an XML-RPC request to the
server.
But first you'd have to make sure Moses is built with XML-RPC.
Regards and good luck
Mathias
?
Mathias M?ller
AND-2-20
Institute of Computational Linguistics
University of Zurich
Switzerland
+41 44 635 75 81
mathias.mueller@uzh.ch
On Fri, Dec 16, 2016 at 10:32 AM, Shubham Khandelwal <skhlnmiit@gmail.com>
wrote:
> Hey Thomas,
>
> Thanks for your reply.
> Using Cube Pruning, the speed is littile bit high, but not that much. I
> will try to play with these parameters.
>
> I have binary moses2 which supports it aswell but it is taking more time
> to than moses. Can you please send/share somewhere your binary moses2 file
> if possible ?
>
> Also, I do not wish to run this command ( ~/mosesdecoder/bin/moses
> -f moses.ini -threads all) every time for every input. Is there any way in
> Moses by which all models will load in memory for forever and I can just
> pass a input and get output in real time without using this command again
> and again.
>
> Looking forward for your response.
>
> Thanks again.
>
> On Fri, Dec 16, 2016 at 1:20 PM, Tomasz Gawryl <tomasz.gawryl@skrivanek.pl
> > wrote:
>
>> Hi,
>> If you want to speed up decoding time maybe you should consider changing
>> searching algorithm. I'm also using compact phrase tables and after some
>> test I realised that cube pruning gives almost exactly the same quality
>> but
>> is much faster. For example you can add something like this to your config
>> file:
>>
>> # Cube Pruning
>> [search-algorithm]
>> 1
>> [cube-pruning-pop-limit]
>> 1000
>> [stack]
>> 50
>>
>> If your model allows you may also try moses2 binary which is faster than
>> original.
>>
>> Regards,
>> Thomas
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 15 Dec 2016 19:12:01 +0530
>> From: Shubham Khandelwal <skhlnmiit@gmail.com>
>> Subject: Re: [Moses-support] Regarding Decoding Time
>> To: Hieu Hoang <hieuhoang@gmail.com>
>> Cc: moses-support <moses-support@mit.edu>
>> Message-ID:
>> <CAHweNTvYeALYrAfJDgDiH51t5_AHSPRV0KwLCABC2td27yoHmA@mail.gm
>> ail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello,
>>
>> Currently, I am using phrase-table.minphr , reordering-table.minlexr and
>> language model (total size of these 3 are 6 GB). Now, I tried to decode on
>> two different machines (8 core-16GB RAM *&* 4 core-40GB RAM) using them.
>> So, During decoding of around 500 words, it took 90 seconds and 100
>> seconds
>> respectively on those machines. I am already using compact phrase and
>> reordering table representations for faster decoding. Is there any other
>> way
>> to reduce this decoding time.
>>
>> Also, In Moses, Do we have distributed way of decoding on multiple
>> machines
>> ?
>>
>> Looking forward for your response.
>>
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>
>
>
> --
> Yours Sincerely,
>
> Shubham Khandelwal
> Masters in Informatics (M2-MoSIG),
> University Joseph Fourier-Grenoble INP,
> Grenoble, France
> Webpage: https://sites.google.com/site/skhandelwl21/
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20161216/d15c73d5/attachment.html
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 122, Issue 31
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 122, Issue 31"
Post a Comment