Urgent.News

What's breaking now, across thousands of outlets.

Tech

Can the QoS burst defaults on FSx for ONTAP be changed from ONTAP 9.19.1, the same as on-premises? I checked on a live file system

Conclusion first: on Amazon FSx for NetApp ONTAP you can change the QoS burst defaults. Not only is the configuration accepted — a brief overshoot above the ceiling (the burst) happened exactly as configured. The catch: you cannot change this setting from the AWS Management Console or the AWS CLI (the AWS API). FSx for ONTAP has two ways in — the AWS-side consoles and APIs, and a separate path…

Conclusion: You can adjust the QoS burst defaults in Amazon FSx for NetApp ONTAP, similar to on-premises systems. However, this setting must be changed using the ONTAP REST API / CLI, not through the AWS Management Console or CLI. The change impacts how a QoS ceiling is exceeded, allowing for tailored performance per workload or tenant.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Running Pandoc in the Browser: WebAssembly, Web Workers, and a 58 MB Module

Every "convert my document" tool I've tried has the same shape: you pick a file, it uploads somewhere, a server does the work, you get a download link back. That's fine for public data.

  • Running Pandoc in browser uses WebAssembly, Web Workers, and 58 MB module
  • Pandoc preserves document semantics through typed abstract syntax tree conversion
  • Module loaded lazily, cached, and executed in Web Worker to maintain UI responsiveness

Beyond Deployment: What's Next for CrescoDB, Plus a Clearer Path to Getting Started

Beyond Deployment: What's Next for CrescoDB, Plus a Clearer Path to Getting Started Building a backend is only part of the work.

  • CrescoDB improving backend workflow and developer insights
  • Upcoming update adds production monitoring and operational visibility tools
  • Server monitoring expanded to include CPU, memory, disk usage, and container resources

More from Tuesday 20 October →