31%
07.06.2019
$ ethstats -c1
eth0: 0.03 Mb/s In 0.14 Mb/s Out - 51.4 p/s In 38.8 p/s Out
requests a single sample and shows a somewhat idle system.
Grand Finale
With a nearly inexhaustible supply
31%
20.03.2014
you get there:
wget http://libguestfs.org/download/builder/fedora-19.xz
The image is only 164MB in size, so the download is done quickly. Back in the main directory of the libguestfs distribution, you
31%
14.03.2013
://objectrocket.com/pricing.
LaCie Announces 5big RAID Solution
LaCie has announced the 5big Thunderbolt Series, a massive new five-bay RAID solution. With five 7200rpm/64MB cache hard disks preconfigured in RAID 0, the LaCie 5
31%
30.11.2025
irrespective of actual system capacity, because the memory is only being allocated, not used. It will then run into the limits of process address space, hitting a wall at 3056MB of allocation; the maximum
31%
14.06.2017
-rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip
with the -9
option (i.e., maximum compression), the resulting file is 268KB. The .gz
31%
14.08.2017
:31 FS_scan.csv
$ gzip -9 FS_scan.csv
$ ls -lsah FS_scan.csv.gz
268K -rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip with the -9
31%
07.01.2014
the space used in the two backup directories and the SOURCE
directory. The SOURCE
directory reports using 9.2MB; backup.0
, the most recent snapshot, also reports using 9.2MB (as it should), and backup.1
31%
24.09.2015
that is 80% parallelizable (20% is serial, primarily because of I/O). For one process, the wall clock time is assumed to be 1,000 seconds, which means that 200 seconds is the serial portion of the application
31%
28.11.2021
: ['localhost:9104']
30
31 # scrape HTTP endpoint check metrics
32 - job_name: blackbox
33 metrics_path: /probe
34 params:
35 module: [http_2xx] # Look for a HTTP 200 response.
36 static
31%
05.12.2014
Twitter to yourself 10 years in the past. Try imagining the amount of data Twitter generates, which some estimates suggest is greater than 100TB of data per day, using 200 bytes per tweet and 500 million
