Skip to content

Highest Output-Speed ReMM SLERP 13B Inference Providers

Ranks providers by their recent typical output speed in tokens per second. Providers without enough recent data remain visible after ranked rows.

Mancer currently ranks first at 33.5 tok/s via mancer/fp8.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed ReMM SLERP 13B Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Mancermancer/fp8
Output speed33.5 tok/sSpeed measurements
500-token response
15.82 s
Response starts
0.90 s
Output speed
33.5 tok/s
Endpoint details
Input price
$0.5 / 1M tokens
Output price
$0.75 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
6.1K
#2Provider / route
NextBitnextbit/bf16
Output speed17.0 tok/sSpeed measurements
500-token response
31.17 s
Response starts
1.76 s
Output speed
17.0 tok/s
Endpoint details
Input price
$0.45 / 1M tokens
Output price
$0.65 / 1M tokens
Uptime (30 min)
96.95%
Context
6.1K

Endpoint data fetched .

ReMM SLERP 13B endpoint guide

How to interpret the Highest Output-Speed ReMM SLERP 13B Inference Providers

2 of 2 ReMM SLERP 13B endpoints currently have the published data required for this ranking. Mancer leads at 33.5 tok/s via mancer/fp8. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How generation throughput is ranked

The output-speed ranking compares recent median generated tokens per second. It favors routes that complete long generations quickly, while first-token latency remains a separate measure of how responsive the endpoint feels at the beginning.

Compare Mancer with the next option

NextBit currently ranks second at 17.0 tok/s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.

Use the route, not only the provider name

ReMM SLERP 13B has 2 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.