wickra/.github/ISSUE_TEMPLATE/performance_regression.md at 91f6f672573a840ac5435fed7aca92026d512419

Files

T

kingchencandGitHub 91f6f67257 Add C# (.NET) binding over the C ABI hub (#226 )

The first language stecker on the C ABI hub: a .NET binding exposing all 514
indicators as idiomatic `IDisposable` classes, generated from `wickra.h`.

## What's here

- **`bindings/csharp/`** — the `Wickra` .NET 8 package. `[LibraryImport]`
  source-generated P/Invoke (`NativeMethods.g.cs`) plus idiomatic wrappers
  (`Indicators.g.cs`), both generated from the committed `bindings/c/include/wickra.h`.
  The binding owns no indicator maths — it only marshals types across the C ABI.
- **Marshalling, verified end-to-end against the native library.** Opaque handles
  cross as `nint` kept alive per call via a `SafeHandle`; `bool` as
  `[MarshalAs(U1)]` (Rust `bool` is one byte); a self-correcting
  `DllImportResolver` validates the loaded library actually exports the Wickra
  ABI. Tests cover one representative per FFI archetype (scalar, candle, pairwise,
  multi-output, bars, profile, values-profile, order-book / array-input) plus
  exact Sma reference values.
- **NuGet packaging** — `dotnet pack` produces `Wickra.<version>.nupkg`; the
  release pipeline stages prebuilt native libraries under `runtimes/<rid>/native/`
  for six target triples (win/linux/osx × x64/arm64).
- **`examples/csharp/`** — nine examples mirroring `examples/c/`: streaming,
  backtest, multi_timeframe, parallel_assets, three strategies, and
  fetch_btcusdt + live_binance.
- **CI** — a `csharp` job on the three OSes builds the C ABI, tests the binding,
  and runs the offline examples. **Release** — a gated `csharp-publish` job packs
  and pushes to NuGet (gated on `NUGET_API_KEY`, independent of the GitHub-release
  job so a C# hiccup never blocks the C/C++ asset release).
- **Docs consistency wave** — README, CONTRIBUTING, CHANGELOG, examples/README,
  the issue / PR templates, `sync-about.yml`, and `.gitattributes`.

The native Python / Node / WASM bindings and the C ABI are untouched; this is
additive. Publishing to NuGet stays gated behind the release tag and the secret.

2026-06-09 14:32:05 +02:00

1.6 KiB

Raw Blame History

name, about, title, labels, assignees

name

about

title

labels

assignees

Performance regression

Report a measurable slowdown, memory blowup, or throughput drop.

[Perf] <indicator / API> regressed in <version>

performance

regression

triage

Summary

Affected code path

Indicator / API: e.g. EMA.update
Binding: Rust / Python / Node / Wasm / C ABI / C# (.NET)
Hot loop or one-shot call?

Versions compared

Version	Throughput / latency / memory	Notes
`0.4.1`	`e.g. 12.3 ns/iter`	baseline (Good)
`0.4.2`	`e.g. 38.7 ns/iter`	regressed

Benchmark / reproducer

cargo bench --bench ema -- --save-baseline new

ema/update              time:   [38.5 ns 38.7 ns 38.9 ns]
                        change: [+213.4% +214.8% +216.1%] (p = 0.00 < 0.05)
                        Performance has regressed.

Hardware / environment

Field	Value
CPU	`e.g. Ryzen 9 9950X, AVX2 + AVX512`
OS / arch	`e.g. Linux 6.8 x86_64`
Toolchain	`rustc 1.x.y`
Build flags	`RUSTFLAGS=...`, `--release`, profile

1.6 KiB Raw Blame History