Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Mild Shock <janburse@fastmail.fm> |
|---|---|
| Newsgroups | sci.logic |
| Subject | How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop] |
| Date | 2026-08-12 01:12 +0200 |
| Message-ID | <115gae9$af67$1@solani.org> (permalink) |
Hi,
How fast is EyeProlog, do we need π-WAM?
Ok, here is a test:
between2(L, L, R) :- !, L = R.
between2(L, _, L).
between2(L, H, X) :- J is L+1, between2(J, H, X).
test :-
between2(1, 100, _),
between2(1, 100, _),
between2(1, 100, _),
fail.
test.
I get for EyeProlog and Dogelog:
/* EyeProlog */
0.476 sec
https://eyereasoner.github.io/eyeprolog/playground
/* Dogelog */
% Zeit 446.020 ms, GC 0.000 ms, Lips 6794 k
https://www.herbrand.ai/
Thats not bad. Now watch π-WAM, the first
AI accelerated Prolog subset, with
JavaScript Workers:
:- ensure_loaded(library(misc/brainfog)).
test2 :-
execute((between(1,100,_),
between(1,100,_),
between(1,100,_))).
?- time(test2).
% Zeit 52.675 ms, GC 0.000 ms, Lips 9 k
true.
BTW: With JavaScript WebGPU the AI acceleration
is even an itch stronger, if the problem can
be parallelized.
Have Fun!
Bye
Back to sci.logic | Previous | Next | Find similar | Unroll thread
How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop] Mild Shock <janburse@fastmail.fm> - 2026-08-12 01:12 +0200
csiph-web