From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Alan Braslau <braslau.list@comcast.net>,
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: final thoughts on experiments with lua
Date: Thu, 10 Jan 2019 01:09:51 +0100 [thread overview]
Message-ID: <2171afd4-23a8-46f5-7356-43976615512a@xs4all.nl> (raw)
In-Reply-To: <20190109133844.30a75887@comcast.net>
On 1/9/2019 9:38 PM, Alan Braslau wrote:
> On Wed, 9 Jan 2019 20:57:21 +0100
> "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:
>
>> 3. Lua's handling of tables is very efficient and fast. For analyzing my
>> Greek texts, I have to use huge tables for morphological parsing, with
>> more than 900,000 entries. Looking up words in these tables is around 3x
>> faster in Lua than in python!
>
> I have found, in my limited use (and understanding) of lua for data analysis is that it is indeed VERY fast, and not only beats python without comparison, it also handles quite large data sets without choking.
and with a bit op optimization one can often squeeze out more
> It has become fashionable to use hardware GPUs to speed-up parallel calculation tasks, and this is now often done using libraries having python bindings. I wonder if python becomes the limiting factor in those applications?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-01-10 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 19:57 Thomas A. Schmitz
2019-01-09 20:12 ` luigi scarso
2019-01-09 20:38 ` Alan Braslau
2019-01-10 0:09 ` Hans Hagen [this message]
2019-01-10 0:08 ` Hans Hagen
2019-01-10 9:27 ` Schmitz Thomas A.
2019-01-10 9:50 ` luigi scarso
2019-01-10 11:11 ` Henning Hraban Ramm
2019-01-10 12:09 ` Hans Hagen
2019-01-10 14:53 ` luigi scarso
2019-01-10 7:03 ` Henning Hraban Ramm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2171afd4-23a8-46f5-7356-43976615512a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=braslau.list@comcast.net \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).