Happy Sunday, #BSDCafeHappy Sunday, #illumosCafeHappy Sunday, #Fediverse

[kotrckapeter@mastodon.uno]

@stefano depends on the size of that pizza 🙂

[radio_azureus@ioc.exchange]

Sending you

🦋💙❤️💋#SwitiLobi 💙💕🌹💐💙🦋

from SR SA

@stefano

#SR #Universal #Love ♾️ #Energy

[pertho@mastodon.bsd.cafe]

@stefano Would love to read a write up on it without giving sensitive information out. I love reading about these types of stories. Do you also tailor the recordsize on the zfs datasets as well?

[stefano@mastodon.bsd.cafe]

@pertho I've written something like this in the past, but I'm taking notes for a future ITNotes blog post 😉

For ZFS - it depends. I usually don't do it, but in some specific use cases I've done it. I can't say if it was useful or not.

[pertho@mastodon.bsd.cafe]

@stefano Something like 16k for mysql data is supposed to be good, plus turning off mysql double writes.

[oxy@social.bsdlab.au]

@stefano depends on the pizza 🍕 😂

[nuintari@mastodon.bsd.cafe]

@stefano Depends whether Dax is with me or not. I have one of those doggie canopy/barriers in the back seat of the truck. It keeps her in the back, and away from the pizza in the front seat. :-p

[litchralee_v6@ipv6.social]

@stefano If it's the Pizza Planet truck from Toy Story, then yes. But otherwise, no.

[stefano@mastodon.bsd.cafe]

@pertho it usually does and yes, double writes are bad there.

[ianthetechie@fosstodon.org]

@stefano @pertho no experience with MySQL in the past 15 years, but it definitely can make a difference for heavy Postgres workloads. And of course a large record size is optimal if the dataset is a bunch of large files.