calc.engineer
REMOTE · CALC.ENGINEER · SCANNED AUG 3
88 free engineering calculators: RF link budgets, LoRa/Meshtastic, PCB, solar, homelab. Keyless.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 89 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability42
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 20141 tokens (~221/item across 91 items; 89 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · calc.engineer
claude mcp add --transport http engineer-calc-calc https://calc.engineer/mcp
[mcp_servers.engineer-calc-calc] url = "https://calc.engineer/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"engineer-calc-calc": {
"type": "remote",
"url": "https://calc.engineer/mcp",
"enabled": true
}
}
} openclaw mcp add engineer-calc-calc --url https://calc.engineer/mcp --transport streamable-http
mcp_servers:
engineer-calc-calc:
url: "https://calc.engineer/mcp" {
"mcpServers": {
"engineer-calc-calc": {
"type": "http",
"url": "https://calc.engineer/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 52
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://calc.engineer/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=calc.engineer | CN=WE1,O=Google Trust Services,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 6c8de0c4441fafea135ce83d632ff978 |
| SANs: calc.engineer, api.calc.engineer, *.api.calc.engineer | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of calc.engineer. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| engineer. | present | 14215 | 8 | Verified |
| calc.engineer. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calc.engineer/mcp | Verified | 200 | |
| http (plaintext) | http://calc.engineer/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
trace_width trace width ~271
Calculates the minimum PCB trace width for a given current using the IPC-2221 standard formula. The IPC-2221 empirical equation relates current capacity to cross-sectional area and temperature rise: I = k * dT^0.44 * A^0.725, where k=0.048 for external layers and k=0.024 for internal layers. Supports configurable copper weight (oz/ft^2) and temperature rise. Also computes approximate DC resistance per centimeter. Essential for power delivery, high-current motor drivers, and ensuring PCB reliability. Chain from voltage_divider or impedance_match to verify trace sizing for computed currents.
| Name | Type | Req | Description |
|---|---|---|---|
| copper_oz | number | — | Copper weight in ounces per square foot. 1 oz/ft^2 = 1.37 mil (34.8 um) thickness. Common values: 0.5, 1, 2. |
| current_amps | number | yes | Required current capacity in amperes (A). |
| layer | string | — | PCB layer type. External layers dissipate heat better (k=0.048); internal layers use k=0.024. |
| temp_rise_c | number | — | Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C. |
| Name | Type | Req | Description |
|---|---|---|---|
| area_mil2 | number | yes | Required cross-sectional area in square mils. |
| resistance_per_cm_mohm | number | yes | Approximate DC resistance per centimeter of trace in milliohms, using copper resistivity. |
| width_mil | number | yes | Required trace width in mils (thousandths of an inch). |
| width_mm | number | yes | Required trace width in millimeters. |
No examples provided.
unit_convert unit convert ~244
Convert between units across 10 categories: length (m, km, mi, ft, in, yd, nmi), mass (kg, lb, oz, g, ton), volume (l, gal, ml, cup, fl_oz), area (m2, ft2, acre, hectare), speed (mps, kph, mph, knot), pressure (pa, psi, bar, atm, mmhg), energy (j, kwh, btu, cal, wh), data (b, kb, mb, gb, tb), time (s, ms, min, hr, day, year), and temperature (c, f, k). Accepts any value with source and target unit abbreviations. Returns the converted result with the formula used.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Source unit abbreviation (e.g., 'km', 'lb', 'f', 'psi', 'kwh'). Case-insensitive. |
| to | string | yes | Target unit abbreviation (e.g., 'mi', 'kg', 'c', 'bar', 'btu'). Case-insensitive. |
| value | number | yes | The numeric value to convert. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Unit category (length, mass, volume, area, speed, pressure, energy, data, time, temperature). |
| formula | string | yes | Human-readable conversion formula applied. |
| from_unit | string | yes | Normalized source unit abbreviation. |
| result | number | yes | The converted value. |
| to_unit | string | yes | Normalized target unit abbreviation. |
No examples provided.
ups_runtime ups runtime ~218
Estimates UPS (Uninterruptible Power Supply) backup runtime from battery specifications and connected load. Takes VA rating, watt rating, load in watts, and battery configuration (count, voltage, amp-hours) to compute effective stored energy after efficiency losses and runtime in minutes and hours. Detects overload conditions when load exceeds the UPS watt rating. Calculates power factor from VA/W ratings. Ideal for server rack planning, homelab power budgeting, network closet UPS selection, and graceful shutdown timer configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| battery_ah | number | — | Capacity per battery in amp-hours (Ah) |
| battery_count | integer | — | Number of batteries in the UPS |
| battery_voltage | number | — | Voltage per battery (V) |
| efficiency | number | — | Inverter/conversion efficiency (0-1), default 0.9 |
| load_watts | number | yes | Connected load in watts |
| va_rating | number | yes | UPS VA (volt-ampere) rating |
| watt_rating | number | yes | UPS real power (watt) rating |
| Name | Type | Req | Description |
|---|---|---|---|
| battery_wh | number | yes | Total battery energy in watt-hours (before efficiency) |
| effective_wh | number | yes | Usable battery energy after efficiency losses (Wh) |
| load_pct | number | yes | Load as percentage of UPS watt capacity |
| overloaded | boolean | yes | True if load exceeds UPS watt rating |
| pf | number | yes | Power factor (watt_rating / va_rating) |
| runtime_hours | number | yes | Estimated backup runtime in hours |
| runtime_minutes | number | yes | Estimated backup runtime in minutes |
No examples provided.
voltage_divider voltage divider ~190
Calculates output voltage, current draw, and power dissipation for a resistive voltage divider. Given an input voltage Vin and two resistor values R1 (upper) and R2 (lower), computes Vout = Vin * R2 / (R1 + R2), divider current, individual resistor power dissipation, and the division ratio. Essential for biasing circuits, level shifting, ADC input scaling, and feedback networks. Use before trace_width to size traces for divider current, or chain from a power supply output to verify signal levels.
| Name | Type | Req | Description |
|---|---|---|---|
| r1_ohm | number | yes | Upper resistor value in ohms (R1), connected between Vin and Vout node. |
| r2_ohm | number | yes | Lower resistor value in ohms (R2), connected between Vout node and ground. |
| vin | number | yes | Input voltage in volts (V). Must be positive. |
| Name | Type | Req | Description |
|---|---|---|---|
| current_ma | number | yes | Current through the divider in milliamps (mA). |
| power_r1_mw | number | yes | Power dissipated by R1 in milliwatts (mW). |
| power_r2_mw | number | yes | Power dissipated by R2 in milliwatts (mW). |
| ratio | number | yes | Voltage division ratio R2/(R1+R2), dimensionless 0-1. |
| total_power_mw | number | yes | Total power dissipated by the divider in milliwatts (mW). |
| vout | number | yes | Output voltage in volts at the R1-R2 junction. |
No examples provided.
voltage_drop voltage drop ~231
Calculates voltage drop across a conductor run given current, wire length, AWG gauge, system voltage, and conductor material (copper or aluminum). Computes round-trip resistance, voltage drop in volts and percent, voltage at the load end, power dissipated in the wire, and NEC compliance flags (3% max for branch circuits, 5% max for feeders). Use this after wire_gauge to verify a specific gauge meets requirements, or to evaluate an existing installation. Critical for solar panel string wiring, EV charger circuits, low-voltage lighting, and any long DC or AC cable run where resistive losses matter.
| Name | Type | Req | Description |
|---|---|---|---|
| conductor | string | — | Conductor material: copper or aluminum |
| current_amps | number | yes | Load current in amperes (A) |
| voltage_v | number | yes | System voltage (V) |
| wire_gauge_awg | number | yes | Wire gauge in AWG (e.g. 14, 12, 10; use negative for large gauges: -3 = 4/0) |
| wire_length_m | number | yes | One-way wire length in meters |
| Name | Type | Req | Description |
|---|---|---|---|
| compliant | boolean | yes | True if voltage drop is within NEC limits (<=3% branch, <=5% feeder) |
| power_loss_w | number | yes | Power dissipated as heat in the conductor (W) |
| resistance_ohm | number | yes | Total round-trip conductor resistance (ohm) |
| voltage_at_load_v | number | yes | Voltage at the load end (V) |
| voltage_drop_pct | number | yes | Voltage drop as a percentage of system voltage |
| voltage_drop_v | number | yes | Voltage drop across the conductor run (V) |
No examples provided.
vswr ~160
Convert between VSWR, return loss, and reflection coefficient — provide any one parameter and get all related impedance-mismatch metrics. Computes VSWR (voltage standing wave ratio), return loss in dB, reflection coefficient (gamma), mismatch loss, and percentage of power reflected vs transmitted. Essential for antenna matching, transmission line analysis, and RF system budgeting. Feeds into link_budget for system-level mismatch accounting.
| Name | Type | Req | Description |
|---|---|---|---|
| reflection_coefficient | number | — | Reflection coefficient magnitude (gamma), 0 to 1 |
| return_loss_db | number | — | Return loss in decibels (positive value, higher is better match) |
| vswr | number | — | Voltage standing wave ratio (>= 1.0, where 1.0 is perfect match) |
| Name | Type | Req | Description |
|---|---|---|---|
| mismatch_loss_db | number | yes | Mismatch loss in decibels |
| power_reflected_pct | number | yes | Percentage of power reflected back toward source |
| power_transmitted_pct | number | yes | Percentage of power delivered to load |
| reflection_coefficient | number | yes | Reflection coefficient magnitude (gamma) |
| return_loss_db | number | yes | Return loss in decibels (positive) |
| vswr | number | yes | Voltage standing wave ratio |
No examples provided.
watts_to_amps watts to amps ~151
Converts electrical power in watts to current in amps (and milliamps) for a given voltage, using the DC power formula P = V * I. Also computes the implied load resistance via Ohm's law (R = V / I) assuming a purely resistive load. This is the most common electrical conversion for circuit design, fuse selection, wire sizing, and breaker rating. Use the output amps value to feed into wire_gauge for conductor sizing or voltage_drop for cable loss analysis. Covers DC circuits; for AC with power factor, adjust watts to true power first.
| Name | Type | Req | Description |
|---|---|---|---|
| voltage_v | number | yes | Voltage in volts (V) |
| watts | number | yes | Power in watts (W) |
| Name | Type | Req | Description |
|---|---|---|---|
| amps | number | yes | Current in amperes (A) |
| implied_resistance_ohm | number | yes | Implied load resistance in ohms assuming resistive load (V/I) |
| milliamps | number | yes | Current in milliamperes (mA) |
| voltage_v | number | yes | Input voltage echoed back (V) |
| watts | number | yes | Input power echoed back (W) |
No examples provided.
wavelength_freq wavelength freq ~122
Convert between radio frequency and wavelength. Provide either frequency in MHz or wavelength in metres, and get the full set of equivalent values: frequency in MHz and GHz, wavelength in metres, centimetres, millimetres, and feet. Essential for antenna dimensioning, waveguide selection, and quick band identification. The fundamental relationship is lambda = c / f where c is the speed of light (299 792 458 m/s).
| Name | Type | Req | Description |
|---|---|---|---|
| freq_mhz | number | — | Frequency in megahertz (MHz) |
| wavelength_m | number | — | Wavelength in metres |
| Name | Type | Req | Description |
|---|---|---|---|
| freq_ghz | number | yes | Frequency in gigahertz (GHz) |
| freq_mhz | number | yes | Frequency in megahertz (MHz) |
| wavelength_cm | number | yes | Wavelength in centimetres |
| wavelength_ft | number | yes | Wavelength in feet |
| wavelength_m | number | yes | Wavelength in metres |
| wavelength_mm | number | yes | Wavelength in millimetres |
No examples provided.
wire_ampacity wire ampacity ~390
Determine minimum wire gauge using NEC Table 310.16 ampacity ratings with full derating. Looks up base ampacity for copper or aluminum conductors at 60°C, 75°C, or 90°C insulation rating, then applies NEC 310.15(C)(1) ambient temperature correction and NEC 310.15(C)(2) conductor count adjustment. Automatically applies the 125% continuous load factor per NEC 210.20(A) when flagged. Returns the minimum AWG that meets the derated requirement, plus a comparison table of all gauges. Different from wire_gauge which focuses on voltage drop — use both together for complete wire sizing. Essential for residential panels, commercial feeders, solar arrays, and EV charging installations.
| Name | Type | Req | Description |
|---|---|---|---|
| ambient_temp_c | number | — | Ambient temperature in °C. NEC base is 30°C. Higher temps require derating. Typical: 30 (indoor), 40 (attic/hot), 45+ (rooftop conduit). |
| conductor | string | — | Conductor material. Copper has higher ampacity; aluminum is lighter and cheaper for large feeders. |
| conductors_in_raceway | integer | — | Number of current-carrying conductors in a single raceway or cable. More than 3 requires derating per NEC 310.15(C)(2). |
| continuous_load | boolean | — | Whether the load operates continuously (3+ hours). NEC requires 125% sizing for continuous loads. Set false for intermittent loads. |
| current_amps | number | yes | Required circuit current in amperes. Use 125% of continuous load per NEC 210.20(A). |
| insulation | string | — | Insulation temperature rating in °C. 60=TW/UF-B, 75=THW/THWN/XHHW (most common), 90=THHN/THWN-2. |
| Name | Type | Req | Description |
|---|---|---|---|
| all_gauges | array | yes | All available gauges with their ampacities for comparison. |
| ambient_correction | number | yes | Ambient temperature correction factor applied (1.0 at 30°C). |
| base_ampacity_a | number | yes | Base ampacity from NEC 310.16 before any derating, in amperes. |
| conductor_count_correction | number | yes | Conductor count correction factor (1.0 for 3 or fewer). |
| derated_ampacity_a | number | yes | Final ampacity after applying ambient temperature and conductor count correction factors, in amperes. |
| insulation_label | string | yes | Insulation rating description. |
| minimum_awg | number | yes | Minimum AWG wire gauge that meets the derated ampacity requirement. |
| minimum_awg_label | string | yes | Human-readable AWG label (e.g. '4/0', '12', '2'). |
| required_ampacity_a | number | yes | Ampacity required to carry the load (includes 125% factor if continuous). |
No examples provided.
wire_gauge wire gauge ~190
Determines the minimum AWG (American Wire Gauge) conductor size for a given current, voltage, one-way cable distance, and maximum allowable voltage drop percentage. Supports copper and aluminum conductors. Computes round-trip resistance, actual voltage drop in volts and percent, and wire cross-sectional area. Essential for DC solar runs, battery bank wiring, EV charging circuits, and low-voltage landscape lighting. NEC recommends 3% max drop for branch circuits and 5% total including feeder. Outputs the smallest AWG that satisfies the drop constraint.
| Name | Type | Req | Description |
|---|---|---|---|
| conductor | string | — | Conductor material: copper or aluminum |
| current_amps | number | yes | Load current in amperes (A) |
| distance_m | number | yes | One-way conductor distance in meters |
| max_drop_pct | number | — | Maximum allowable voltage drop as percentage (default 3%) |
| voltage | number | yes | System voltage (V) |
| Name | Type | Req | Description |
|---|---|---|---|
| actual_drop_pct | number | yes | Actual voltage drop percentage with recommended gauge |
| actual_drop_v | number | yes | Actual voltage drop in volts |
| insufficient | boolean | yes | True if even the largest AWG (4/0) cannot meet the voltage drop target |
| recommended_awg | number | yes | Recommended AWG gauge number (smaller number = thicker wire) |
| recommended_awg_label | string | yes | Human-readable AWG label (e.g. '10' or '0000 (4/0)') |
| resistance_per_m | number | yes | Resistance per meter of the recommended gauge (ohm/m) |
| wire_area_mm2 | number | yes | Cross-sectional area of recommended gauge in mm^2 |
No examples provided.
wireguard_mtu wireguard mtu ~202
Calculate the optimal MTU for a WireGuard VPN tunnel interface with a detailed overhead breakdown. Accounts for WireGuard header (32 bytes), outer IP header (20 bytes IPv4 or 40 bytes IPv6), UDP header (8 bytes), and optional PPPoE encapsulation (8 bytes). Prevents fragmentation and PMTUD black holes by computing the maximum inner packet size that fits within the physical link MTU. Essential for WireGuard setup on residential ISP connections (PPPoE), IPv6 tunnels, and any VPN where incorrect MTU causes slow or stalled connections.
| Name | Type | Req | Description |
|---|---|---|---|
| interface_mtu | integer | — | MTU of the underlying physical or virtual network interface in bytes |
| ipv6 | boolean | — | Whether the outer (transport) IP header uses IPv6 (40 bytes) instead of IPv4 (20 bytes) |
| over_pppoe | boolean | — | Whether the link uses PPPoE encapsulation (adds 8 bytes of overhead) |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | yes | Itemized breakdown of each overhead component in bytes |
| overhead_bytes | number | yes | Total encapsulation overhead in bytes subtracted from interface MTU |
| wireguard_mtu | number | yes | Optimal MTU to set on the WireGuard tunnel interface in bytes |
No examples provided.
zfs_capacity zfs capacity ~225
Calculate usable ZFS pool capacity for any RAID level including stripe, mirror, raidz1, raidz2, and raidz3. Computes raw capacity, parity overhead, data disk count, usable terabytes after ZFS metadata overhead (checksums, block pointers, uberblocks), and storage efficiency percentage. Essential for planning NAS builds, TrueNAS/ZFS server storage, and estimating how much usable space a given disk configuration will provide. Supports variable disk sizes and configurable metadata overhead.
| Name | Type | Req | Description |
|---|---|---|---|
| disk_count | integer | yes | Total number of physical disks in the pool |
| disk_size_tb | number | yes | Size of each individual disk in terabytes |
| metadata_overhead_pct | number | — | Percentage of raw capacity consumed by ZFS metadata, checksums, and internal structures |
| raid_type | string | — | ZFS RAID level: stripe (no redundancy), mirror (2-way), raidz1/2/3 (single/double/triple parity) |
| record_size_kb | number | — | ZFS record size in kilobytes, affects compression and performance |
| Name | Type | Req | Description |
|---|---|---|---|
| data_disks | number | yes | Number of disks (or disk-equivalents) available for data storage |
| efficiency_pct | number | yes | Storage efficiency as a percentage of raw capacity |
| parity_disks | number | yes | Number of disks (or disk-equivalents) consumed by parity/mirroring |
| raw_tb | number | yes | Total raw capacity across all disks in terabytes |
| usable_tb | number | yes | Usable capacity after parity and metadata overhead in terabytes |
No examples provided.
zfs_ram zfs ram ~251
Calculate recommended RAM and ARC sizing for a ZFS storage pool based on workload type, pool size, deduplication status, and L2ARC cache size. Computes minimum and recommended RAM in gigabytes, ARC target size, and dedup table overhead. Accounts for workload-specific IO patterns: NAS (sequential, 1GB/TB), database (random, 2GB/TB), virtualization (mixed, 1.5GB/TB). Deduplication adds approximately 5GB per TB for the DDT. L2ARC index requires 1GB RAM per 10GB of L2ARC. Essential for TrueNAS, FreeNAS, and custom ZFS server builds.
| Name | Type | Req | Description |
|---|---|---|---|
| dedup_enabled | boolean | — | Whether ZFS deduplication is enabled (significantly increases RAM requirements) |
| l2arc_size_gb | number | — | Size of L2ARC (read cache SSD) in gigabytes; requires additional RAM for index |
| pool_size_tb | number | yes | Total usable pool size in terabytes |
| workload | string | — | Primary workload type: general (mixed), nas (sequential reads/writes), database (random IO), virtualization (mixed random) |
| Name | Type | Req | Description |
|---|---|---|---|
| arc_target_gb | number | yes | Target ARC (Adaptive Replacement Cache) size in gigabytes |
| dedup_table_gb | number | yes | Estimated dedup table (DDT) RAM requirement in gigabytes |
| min_ram_gb | number | yes | Minimum recommended RAM in gigabytes for stable operation |
| notes | string | yes | Human-readable sizing rationale and recommendations |
| recommended_ram_gb | number | yes | Recommended RAM in gigabytes for optimal performance (2x minimum) |
No examples provided.