<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GNU TAR on nagg.eu</title><link>https://nagg.eu/tags/gnu-tar/</link><description>Recent content in GNU TAR on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Oct 2018 18:00:00 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/gnu-tar/index.xml" rel="self" type="application/rss+xml"/><item><title>GNU TAR and memory caching</title><link>https://nagg.eu/gnu-tar-and-memory-caching/</link><pubDate>Wed, 10 Oct 2018 18:00:00 +0000</pubDate><guid>https://nagg.eu/gnu-tar-and-memory-caching/</guid><description>&lt;p&gt;Guess it is time to write my first post using Hugo.&lt;br&gt;
Yesterday I downloaded a torrent consisting of 2 years worth of 4chan posts,
the plan was to mess with it and use the data to train a chatbot.&lt;br&gt;
Dealing with big datasets is always fun because even the easiest tasks tend to
get complicated, for example extracting the data from a ~3 GB tar.gz compressed
archive was a challenge by itself.&lt;br&gt;
Running “tar -xzvf archive.tar.gz” resulted in TAR/the Linux kernel eating the
whole available memory to use it as cache, when that was down to ~200 MB of
free RAM my workstation started lagging so hard that even Xorg was freezing for
a couple of seconds every 20 or so seconds.&lt;br&gt;
To solve the issue what I did was running the following commands:&lt;/p&gt;</description></item></channel></rss>