Skip to main content

Posts

Home Lab Front-End Data Store: Designing for Predictable I/O Performance

Based on a LinkedIn post originally published on 8 April 2026 Performance in my home-lab platform is the result of architectural choices rather than one isolated optimisation. The system does not depend on a single exceptionally fast disk or one configuration parameter intended to solve every workload problem. Instead, the design combines: memory-backed read caching through ZFS ARC; storage distributed across several back-end nodes; a dedicated storage network; asynchronous handling where the required write semantics permit it; SSD-backed staging for temporary I/O pressure; and separation between client-facing and back-end responsibilities. The objective is not maximum performance in one synthetic benchmark. It is stable, explainable behaviour across mixed workloads and during ordinary background activity. Peak throughput is useful. Predictable throughput under changing conditions is operationally more valuable. The client sees one service, not the back-end complexity HG000009 presents...
Recent posts

TV Serie - Dark Matter (2024 ) - Season 2

  Log Episode 1 [Fri, Aug 28, 2026] - 2026-Sep-01 Episode 2 [Fri, Sep 4, 2026] - 2026-Sep-04 Episode 3 [Fri, Sep 11, 2026] - 2026-Sep-16 Episode 4 [Fri, Sep 18, 2026] - 2026-Oct-11 Episode 5 [Fri, Sep 25, 2026] - 2026-Oct-11 Episode 6 [Fri, Oct 2, 2026] - 2026-Oct-11 Episode 7 [Fri, Oct 9, 2026] - 2026-Oct-11 Episode 8 [Fri, Oct 16, 2026] - 2026-Nov-16 Episode 9 [Fri, Oct 23, 2026] - 2026-Nov-16 Episode 10 [Fri, Oct 30, 2026] - 2026-Nov-16

Movie - Heart of the Beast (2026)

 

Movie - The Runner (2026)

 

Movie - Toy Story 5 (2026)

  A woman, even a toy, internalizes the momentary, non-existent feelings of a child, makes them more than what they are, decides that everyone else is wrong and only she is right, and decides that she has to change the world to accommodate her views... Where have I seen this before?

Movie - Star Wars: The Mandalorian and Grogu (2026)

 

TOMS - Designing the Architecture in Layers: Domain Objects, Graphics, Views and Business Rules

As the event-planning application grows, individual classes are becoming less interesting than the relationships between groups of classes. I have already spent considerable time thinking about Guests, Groups, Tables, Chairs, contact information, the Event Document and the graphical objects used to describe a venue. Each of those concepts can be designed reasonably well in isolation. But a collection of well-designed classes does not automatically produce a well-designed application. The next question is architectural: How should all these classes be organised so that the business data, graphical representation, user interface and business rules do not gradually become one enormous interconnected structure? This is particularly important for a desktop application because the same underlying information may appear in many places at the same time. A Guest may appear in a Guest list. The same Guest may appear as a name beside a Chair on the floor plan. ...