Hi folks, my name is Kevin Veale. I'm a Senior Lecturer in Media Studies and fiction author.

https://wheretofind.me/@krveale

"He/Him." Tangata Tiriti. Pakeha.

I'm into a wide variety of popular culture stuff in lots of different media forms, some of which I write about academically. I reshare stuff that amuses me, post random thoughts or resources, and generally hang out.

You must log in to comment.

in reply to @NireBryce's post:

I follow this practice, but a few things to note:

  • The size of the buffer should be proportional to the capacity of the disk/volume. I aim for 15%.
  • Instead of a buffer file, I use a buffer partition - this way I can control the location of the data on the disk itself, placing it at the end of the disk (where performance is worse), therefor reserving the faster performing areas for actual data.
    • This only applies to HDDs. I still do this on SSDs just for consistency but it has no impact on performance.
    • This does have the caveat that you need to be using a filesystem for the data partition that supports online extending (or offline extending if you can deal with that).

yeah! i wrote about it because i was reminded by having 6kb left in my home dir thanks to Go and a github install script sudo curl | bash misfiring and installing Several Gigabytes of dependencies for something.

it's good additional context :)

in reply to @SomeEgrets's post: