https://github.com/xnacly/treewalk-vs-jit-with-go-plugins
Evaluating the trade-offs of using the Go-plugin API for JIT compilation while comparing the approach with a tree-walk interpreter
https://github.com/xnacly/treewalk-vs-jit-with-go-plugins
academic-paper bytecode-interpreter jit-compiler
Last synced: about 2 months ago
JSON representation
Evaluating the trade-offs of using the Go-plugin API for JIT compilation while comparing the approach with a tree-walk interpreter
- Host: GitHub
- URL: https://github.com/xnacly/treewalk-vs-jit-with-go-plugins
- Owner: xNaCly
- Created: 2024-01-03T23:57:03.000Z (over 1 year ago)
- Default Branch: master
- Last Pushed: 2024-05-28T12:08:10.000Z (11 months ago)
- Last Synced: 2024-05-29T03:34:16.397Z (11 months ago)
- Topics: academic-paper, bytecode-interpreter, jit-compiler
- Language: TeX
- Homepage:
- Size: 5.25 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Comparing a Tree-walk Interpreter with JIT compilation and embedding via Go-plugins
> Evaluating the trade-offs of using the Go-plugin API for JIT compilation
> while comparing the approach with a tree-walk interpreter
## Abstract
The goal of this paper is to evaluate whether the usage of the Go plugin
API is feasible for just-in-time compilation of a query language intended
for a high performance in memory data storage. This evaluation is done
based upon the criteria of the ease of usability, performance and the
robustness of the resulting implementation. For the sake of comparison the
query language as well as its features are introduced. A just in time
compiler is implemented and benchmarked against the same expressions
evaluated with the currently employed tree walk interpreter. The paper
explores the different possibilities for accessing the Go compiler, working
with the Go plugin API and highlights several benchmarks comparing the
performance of the new JIT compiler and the previous language evaluation
implementation.