-
The [iOS](https://github.com/maplibre/maplibre-native/pull/1873) and [Android](https://github.com/maplibre/maplibre-native/pull/1850) rendering benchmarks should be run on CI.
Like all our instrume…
-
The developer documentation (https://gwb.readthedocs.io) is currently still mostly missing. This issue keeps track of the API and Developer manual which still need to be written. All pages already hav…
-
### Checklist
- [x] I've read the [contribution guidelines](https://github.com/autowarefoundation/autoware/blob/main/CONTRIBUTING.md).
- [X] I've searched other issues and no duplicate issues were…
-
This is a sketch for some sections of documentation that should go in the README.
## What to test?
Ideally, benchmarks measure how long *our project* (dask, distributed) spends doing something, …
-
__The problem__
Currently our character data is represented as follows:
```haskell
newtype ContinuousCharacter = CC (ExtendedReal, ExtendedReal)
-- where for the sake of completeness ExtendedRea…
-
Once the self-hosted compiler (#89) can build meaningful programs, it needs benchmarks to test the performance of various things. Such benchmarks should be run by the CI on every commit, and it should…
-
Currently, continuous transform uses a number of optimizations in order to avoid excessive work when the changes between checkpoints are small.
Most notably, transform identifies terms that changed …
-
**Question**
I run a fio test with longhorn 1.1.2, the result is kind of disappointing. On native ssd, 4K random write could reach IOPS=42.5k, BW=166MiB/s, while on longhorn, only get about IOPS=6k…
-
The discussion of benchmarks in https://github.com/openmm/openmm-org/pull/86 rekindled the concept of providing useful tools to users to auto-tune simulation performance for their particular system/ha…
-
As mentioned in #4, in order to avoid performance regressions, it would be great to run some benchmarks on the different parts of the API.
The most expensive operation is clearly `UserInterface::bu…
hecrj updated
2 years ago