-
# What is this issue?
A central place to discuss the issue of a Cabal exact-printer so that we can push forward the work all in one place. Currently, The discussion stretches back across many issu…
-
We've already had a lot of discussion on this. Lets summarise algorithms here.
This is about small, fast PRNGs. Speed, size and performance in tests like PractRand and TestU01 is of interest here; …
-
Currently, we run benchmarks to improve (or at least not regress) on the performance of Boa. This is a very good approach, but we are missing proper benchmarking against other JavaScript engines.
P…
-
@matentzn et al. published a very useful article a few (well, ok, 6) years ago:
> Matentzoglu, N., Malone, J., Mungall, C. et al. MIRO: guidelines for minimum information for the reporting of an onto…
-
I tried to simplify the benchmarks a bit to understand a bit better what was going on, as I found weird a 10x speed-up of NumPy vs. PyTorch (we know that there is a bit of extra overhead in PyTorch, b…
-
I am trying out orion with various configurations from the given example.. The example given at `https://github.com/eth-easl/orion/tree/main/artifact_evaluation/example` works well. However the same f…
-
## 🐛 Bug
Running the upstreamed benchmarking scripts with the following command results in an unexpected error.
```bash
python xla/benchmarks/experiment_runner.py \
--suite-name torchbe…
-
Hi @mtrudel
I didn't find the discussion section open for this repo, so I am leaving this here.
I feel like there is a need to load test WebSocket connections on Phoenix + Bandit, similar to w…
sksar updated
7 months ago
-
```
import React, {useState} from 'react';
import * as Y from 'yjs'
import YjsQuill from "./YjsQuill";
function App() {
const range = [...Array(100).keys()]
const ydoc = new Y.Doc()
return (
…
-
Hi @yamt ,
it is really cool that you put so many Wasm runtimes on your benchmarks for comparison!
I have a few questions though.
What hardware did you run the benchmarks on? Would be cool if you…