So dropped a *FANCY* new micro-mirror off at the shipping company today. This will be our first
Optiplex 9020 micro (how appropriate?) based micro-mirror. Couple of nice advantages over our trusty T620s: actually good nics, beefier cpu, more ram.

Downside: costs more (I mean, duh?)

The mirror is sponsored by and is going to be our first international mirror! Go


Internal pictures because those are way more interesting!

So lets talk storage for 10 seconds. As we've noted before the beauty of these systems is that the storage needs to be only a bit faster than the network, and turns out an ssd on the sata bus can move about 560MB/s and 530MB/s read/write respectively. Turns out, we only need to be faster than 125MB/s on both of those ;-)

So we'll serve data off the 2TB drive, and there's a 1TB drive we boot from and COULD put more data on (also sata)

· · Web · 1 · 0 · 1

Now there *IS* a gotcha with the storage if you understand storage well: while the drives can move data at 500someMB/s doing filesystem walks will is a *LOT* of random i/o all over the place, there's a reason that rsync can be so brutal to a mirroring infrastructure. SSDs help, their random i/o is quite good. We just don't serve rsync from the MMs. After that there's, 16GB of ram which will end up most disk cache.

And if I get back around to it, pushing syncdiff(erent) is a pretty smart choice here and I think it's something I might poke around and see what I can do with it...

Sign in to participate in the conversation
A Social Front Organization

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!