Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #97480 > unrolled thread

Re: ANN: Dogelog Player 1.1.4 (Generational GC)

Started byMild Shock <janburse@fastmail.fm>
First post2024-01-20 00:59 +0100
Last post2024-01-20 11:06 +0100
Articles 2 — 1 participant

Back to article view | Back to comp.lang.javascript

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: ANN: Dogelog Player 1.1.4 (Generational GC) Mild Shock <janburse@fastmail.fm> - 2024-01-20 00:59 +0100
    Re: ANN: Dogelog Player 1.1.4 (Generational GC) Mild Shock <janburse@fastmail.fm> - 2024-01-20 11:06 +0100

#97480 — Re: ANN: Dogelog Player 1.1.4 (Generational GC)

FromMild Shock <janburse@fastmail.fm>
Date2024-01-20 00:59 +0100
SubjectRe: ANN: Dogelog Player 1.1.4 (Generational GC)
Message-ID<uof2cb$m4av$2@solani.org>
Dogelog Player is a 100% Prolog written Prolog
interpreter. We started seeding the implementation
of a common HTTP Server library for all targets
JavaScript, Python and Java. Lets take a snapshot of
the current API and report some performance experience.

We could complete a minimal library(spin) and
demonstrate the correct UTF-8 HTTP streaming of a
text stream. We then measured the local delivery of
a hobbit.txt file of 50'000 bytes, we also run
against SWI-Prolog. We were positively surprised by
the performance of JavaScript, Java and SWI-Prolog.
Only the Python performance was a little disappointing.


See also:

Streaming HTTP for Dogelog Player
https://twitter.com/dogelogch/status/1748477496364818517

Streaming HTTP for Dogelog Player
https://www.facebook.com/groups/dogelog

[toc] | [next] | [standalone]


#97875

FromMild Shock <janburse@fastmail.fm>
Date2024-01-20 11:06 +0100
Message-ID<uog5un$ml7a$3@solani.org>
In reply to#97480
Our initial testing with CPython was consistently
very disappointing, so that we switched to PyPy,
the alternative JIT-ing implementation of Python.
With running Doglog Player via PyPy it becomes
comparable in performance to the JavaScript target,
both targets now only lack by ca 50% behind the
Java target and SWI-Prolog.

See also:

Streaming HTTP for Dogelog Player [corrected]
https://twitter.com/dogelogch/status/1748646455999332354

Streaming HTTP for Dogelog Player [corrected]
https://www.facebook.com/groups/dogelog

Mild Shock schrieb:
> 
> Dogelog Player is a 100% Prolog written Prolog
> interpreter. We started seeding the implementation
> of a common HTTP Server library for all targets
> JavaScript, Python and Java. Lets take a snapshot of
> the current API and report some performance experience.
> 
> We could complete a minimal library(spin) and
> demonstrate the correct UTF-8 HTTP streaming of a
> text stream. We then measured the local delivery of
> a hobbit.txt file of 50'000 bytes, we also run
> against SWI-Prolog. We were positively surprised by
> the performance of JavaScript, Java and SWI-Prolog.
> Only the Python performance was a little disappointing.
> 
> 
> See also:
> 
> Streaming HTTP for Dogelog Player
> https://twitter.com/dogelogch/status/1748477496364818517
> 
> Streaming HTTP for Dogelog Player
> https://www.facebook.com/groups/dogelog

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.javascript


csiph-web