Back
NoteMay ’23

Open it where it is

On SolidFire’s Volumes view, a volume opens under its own row instead of on a screen of its own. The list moves to make room, and nobody loses their place six thousand rows deep.

Typeface

A SolidFire cluster could hold thousands of volumes, and the Volumes view is where a storage admin spends the day. The question that brings them to it is usually an application team’s: their database is slow. Which volume, and why?

The previous UI answered by opening the volume on a screen of its own. When I redesigned the Volumes view in 2015, opening a volume stopped leaving the grid. Its throughput, IOPS and latency open under its row, on one time axis, and the rest of the list stays where it was.

Six thousand rows deep, losing your place is the expensive part. The row is the first step of the diagnosis, and a scan down the list is how you find the volume worth opening. If the first one you open isn’t the culprit, the next candidate is a few rows away. A separate screen turns each of those checks into a trip out and a search back in.

The choice cost something, and I made it on purpose. The drilldown pushes the rows below it down instead of opening over them, so the list moves, but nothing it held is hidden. An overlay would have kept every row still. It would also have covered the rows you might want next.

When the list is the work, detail should open inside it, even if that means the list has to move. Movement you caused, right under the row you clicked, is easy to follow. A new screen throws your place away, and a panel on top hides the neighbours you were about to compare.

The test is short. If the next question is likely to be about the row beside the one you opened, the detail belongs in the list.