Skip to content
DispatchAtlas
Search

Comparison

How DispatchAtlas compares to scheduling-benchmark platforms, optimization frameworks, and fog–edge–cloud simulators — one curated scheduling-instance atlas with every peer cited.

DispatchAtlas is a toolkit for scheduling and optimization across distributed-computing environments, built around a curated, citation-backed catalog of problem instances — not only a solver library, a benchmark list, or a network simulator.

What sets DispatchAtlas apart

No single peer below is the differentiator — the combination is. DispatchAtlas pairs a curated, citation-backed catalog of scheduling and edge–fog–cloud optimization instances with a capability-typed solver registry, built-in non-parametric statistical comparison, and a public inspection portal whose in-browser suite builder composes ready-made or fully custom benchmark suites from the whole catalog and downloads them as JSON, CSV, or a bundle with no backend. Each of those pieces exists elsewhere; none of the peers below ships all of them together.

The nearest challengers deserve honest naming. jMetal ships an experimental study harness with non-parametric statistics, but no scheduling-instance catalog or inspection portal. job-shop-lib and the TU/e Job Shop Scheduling Benchmark ship rich scheduling instances, but no citation-per-instance curation, bundled statistics, or portal. WfCommons ships trace-backed workflow generators, but scores no optimizers and runs no statistics. DispatchAtlas is the project that holds all five capabilities at once.

This page is the canonical statement of that positioning; other surfaces link here rather than restating it.

These tables compare platform capabilities — what each project ships — not performance. Performance evidence comes from the statistical analysis exports, never from this page. The tables are grouped into bands of comparable projects, keeping the same five capability columns throughout. Each peer links to its canonical citation; full sources are listed at the foot of the page. ✅ provided, ⚠️ adjacent or partial, ❌ not provided.

DispatchAtlas appears once, in the first band, and its ✅✅✅✅✅ row holds across every band that follows.

Scheduling benchmark platforms and solvers

PlatformCurated scheduling-instance catalogEdge–fog–cloud as benchmark instancesCapability-typed solver registryBuilt-in statistical comparisonPublic inspection portal
DispatchAtlas
job-shop-lib⚠️⚠️
Job Shop Scheduling Benchmark⚠️
PyJobShop⚠️
schlably
OR-Tools CP-SAT

OR-Tools CP-SAT is the dominant exact scheduling solver — DispatchAtlas does not compete with it. Optional exact adapters wrap solvers like it behind extras, and the capability matrix records exact optimization as an adapter capability: wrapped, not rivaled. job-shop-lib bundles classic instances alongside RL/GNN environments; the TU/e suite unifies JSP, FJSP, and online-FJSP environments for learning and non-learning methods; PyJobShop provides constraint-programming modeling evaluated on 9,000+ literature instances across machine and project scheduling; schlably is a deep-reinforcement-learning scheduling-experiment framework. None curates citation-per-instance provenance, ships statistical gates, or publishes an inspection portal — the ⚠️ marks flag instances that ship without curated citation metadata.

General optimization benchmarking and metaheuristic frameworks

PlatformCurated scheduling-instance catalogEdge–fog–cloud as benchmark instancesCapability-typed solver registryBuilt-in statistical comparisonPublic inspection portal
COCO⚠️
IOHprofiler
pymoo⚠️⚠️
jMetal / jMetalPy⚠️
Nevergrad⚠️⚠️⚠️
mealpy⚠️
NiaPy⚠️

COCO benchmarks a different problem class (continuous black-box functions); its suite family spans single-, bi-objective, large-scale, mixed-integer, and constrained variants with a public data archive. IOHprofiler benchmarks iterative heuristics and offers a hosted web analyzer. jMetal and jMetalPy are included precisely because they are not strawmen: they ship experimental studies with non-parametric statistics, yet no scheduling catalog or portal. Nevergrad provides rank plots and an experiment-and-plotting module over hundreds of optimizers, but not non-parametric inference. pymoo, mealpy, and NiaPy provide rich algorithm collections and synthetic test functions rather than a capability-typed registry oriented to scheduling.

Fog and edge simulators

PlatformCurated scheduling-instance catalogEdge–fog–cloud as benchmark instancesCapability-typed solver registryBuilt-in statistical comparisonPublic inspection portal
iFogSim2⚠️
EdgeCloudSim⚠️
LEAF⚠️
YAFS⚠️
EdgeSimPy⚠️

These model edge–fog–cloud networks as discrete-event simulations (⚠️), not as a benchmark suite an optimizer is scored on. EdgeCloudSim v5.0 runs on the current CloudSim 7.0.0-alpha core with new tutorials. YAFS is the Python fog simulator closest in spirit to the continuum families, and its placement problems are what DispatchAtlas re-expresses as scored benchmark instances; EdgeSimPy is the most recent Python edge-resource-management simulator.

Cloud and workflow simulation platforms

PlatformCurated scheduling-instance catalogEdge–fog–cloud as benchmark instancesCapability-typed solver registryBuilt-in statistical comparisonPublic inspection portal
CloudSim / CloudSim 7G⚠️
WfCommons⚠️⚠️⚠️
WRENCH⚠️

These are simulators and trace/generator frameworks, not optimizer benchmarks — the same honest framing the fog band uses. WfCommons's trace-to-generator-to-benchmark pipeline is the strongest conceptual analogue of the platform's trace-backed ambitions, and it is exactly where DispatchAtlas is weakest today: one calibrated-synthetic profile, the ⚠️ trace-backed row in the capability matrix below.

Optuna is complementary tooling, not a peer: it is a hyperparameter tuner, so solver hyperparameters can be tuned by it, but it ships no scheduling instances and no provenance story — which is why "why not just use Optuna?" has a one-line answer. Cite Optuna (Akiba et al., KDD 2019).

How to read the marks:

  • Curated scheduling-instance catalog — a versioned, citation-backed set of scheduling and permutation problem instances. The scheduling peers ship instances but not citation-per-instance curation; the optimization frameworks ship synthetic test problems; the simulators ship no optimization-instance catalog.
  • Edge–fog–cloud as benchmark instances — heterogeneous placement and communication problems exposed as optimization instances. The simulators model edge–fog–cloud networks (⚠️), but as discrete-event simulations, not as a benchmark suite an optimizer is scored on.
  • Capability-typed solver registry — solvers carry declared objectives, constraints, and capability metadata. The metaheuristic libraries provide rich algorithm collections (⚠️) but not a capability-typed registry oriented to scheduling.
  • Built-in statistical comparison — non-parametric tests and effect sizes bundled with the toolkit. COCO, IOHprofiler, and jMetal ship dedicated statistical tooling.
  • Public inspection portal — a browsable, public-safe data surface. COCO publishes a workshop data archive (⚠️); IOHanalyzer offers a hosted web analyzer.

What DispatchAtlas does not provide

This is the honest reverse gap — each item names the peer that has what DispatchAtlas does not, and mirrors an existing ❌ or ⚠️ row in the capability matrix below.

  • No discrete-event simulation — the fog and cloud simulators (CloudSim, iFogSim2, EdgeCloudSim, WRENCH) model time-stepped network and platform dynamics; DispatchAtlas scores optimizers on instances instead.
  • No dynamic-arrival or online-rescheduling generators — the TU/e suite ships online-FJSP environments; every bundled DispatchAtlas generator is static.
  • No learning-agent training environments — job-shop-lib and schlably ship RL/GNN environments; DispatchAtlas's learning interfaces are partial.
  • Single-host campaign execution — Nevergrad executes large parallel experiment batteries; DispatchAtlas runs sequential, threaded, bounded, and replay execution on one host.
  • One calibrated-synthetic trace profile — WfCommons ships validated trace-derived generators over real workflow archives; DispatchAtlas bundles a single calibrated-synthetic profile.

Sources

DispatchAtlas stance

AxisDispatchAtlas stance
Domain contractsTyped scheduling objects, validation, provenance, and deterministic seeds are the foundation.
BenchmarksCatalog metadata includes characterization, citation status, evidence class, and content hashes.
SolversBaselines, optional exact adapters, metaheuristics, scheduling variants, and the NDSO solver family share registry metadata.
Reproducible campaignsCampaigns declare run ids, budgets, stop criteria, outputs, and environment capture.
AnalysisStatistical summaries, effect sizes, figures, and portal bundles are deterministic exports.
WebsiteDocs and portal pages consume static public-safe data bundles.

Capability Matrix

Each status is verified against the shipped packages and the public portal bundles named in the basis column: ✅ supported today, ⚠️ partial, ❌ absent.

CapabilityStatusBasis
Typed scheduling domain contracts with validation, provenance, and deterministic seedsdispatchatlas.core problem, schedule, and hashing contracts
Benchmark catalog with quantitative characterization metricsbenchmark-catalog.json records carry per-instance characterization
Citation-backed benchmark family inventorybenchmark-families.json — every family row is citation-backed
Named-solver registry with declared capabilities and citationssolver-registry.json and solver-capabilities.json
Exact optimization adapters (optional extras plus two native bounded solvers)seven exact entries in solver-registry.json; third-party backends stay behind extras
Constructive dispatching and metaheuristic baselinesdispatching and metaheuristic groups in solver-registry.json
Many-objective optimization (reference-point niching)many_objective contract in solver-capabilities.json
Named multi-objective quality indicatorsfour cited indicators in solver-capabilities.json
Constraint accounting with service-level breach and penalty pathsconstraint_support contract in solver-capabilities.json
Robustness aggregation (worst-case and CVaR)robustness contract in solver-capabilities.json
Solver recommendation from declared metadatasolver-recommender.json axes and policy
Learned-model recommendation confidence above metadata-only⚠️the supervised selector ships, but published bundles carry metadata-only confidence
Learning and hybrid interfaces⚠️two of seven named interfaces are implemented; five are registered as deferred
Trace-backed benchmark profiles⚠️one calibrated-synthetic profile; no bundled trace-backed profile — trace-backed instances arrive only through the operator-run WfCommons ingest
Dynamic-arrival or online-rescheduling generatorsthe taxonomy declares the dimension; every bundled generator is static
Accelerated batch-scoring kernelsthe batch-scoring profile records a standard-library kernel
Multi-host campaign executionexecution modes are sequential, threaded parallel, bounded, and replay on one host
Campaign checkpoint, resume, and replay verificationdispatchatlas.lab repository, checkpoint, and replay contracts
Statistical-power run-count floor and fair-comparison gaterun-count policy and fair-comparison invariant in dispatchatlas.lab
Non-parametric statistical analysis with effect sizesdispatchatlas.analytica exports; feature row in platform-comparison.json
Reproducible hashed download bundlesdownloads.json records a content hash and size per bundle
In-browser benchmark-suite builder (ready-made and custom suites, client-side export)BenchmarkExplorer over benchmark-catalog.json; exported via lib/download.ts (JSON, CSV, ZIP)