15%
30.01.2020
tottime percall cumtime percall filename:lineno(function)
148/1 0.001 0.000 156.745 156.745 {built-in method builtins.exec}
1 149.964 149.964 156.745 156.745 md_002.py:3
15%
18.07.2013
-generation SSD, being tested on a 3Gbps SATA 2 bus.
I have an 80GB Intel 320 SSD, performing remarkably close to its specified sequential read rating of 270MBps [1], but it is the second-generation drive
15%
26.02.2014
-sent: 22,334 (total) 0/s (Per-Sec)
pkts-recv: 68,018 (total) 2/s (Per-Sec)
lo
Bytes-sent: 2.55 K (total) 0.00 B/s (Per-Sec)
Bytes
15%
11.02.2016
.40 <- < 71% idle >
0 1.00 0.00 0.37 0.00 0.00 0.06 0.00 0.00 0.00 98.57
1 100.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2 3.77 0.00
14%
16.03.2021
=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=1420KiB/s][w=355 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3377: Sat Jan 9 15:31:04 2021
write: IOPS=352, BW=1410Ki
14%
31.07.2013
.
The first thing that strikes me in this strace output is that I’ve graduated from one write()
function to two. The first writes 4,096 bytes, and the second writes 3,904 bytes. When I divide the total of 8,000
14%
17.08.2011
being used.
It doesn’t matter what platform you use: If it’s pay as you go, you’ll want to monitor it to prevent your $1,000-a-month bill turning into $10,000 a month.
In the tradition of programmers
14%
30.11.2025
Destination MAC address
Listing 1
Nemesis arp Packets
01 $ while true
02 > do
03 > sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 -D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2
14%
04.12.2013
today is Fortran 90, even though more current versions (Fortran 95, Fortran 2003, and even Fortran 2008) are available. I took the C code in the previous article (Listings 2C and 3C) and rewrote
14%
01.08.2019
source JIT compiler that translates a subset of Python and NumPy [2] code into fast machine code at run time; hence, the "JIT" designation. Numba uses the LLVM [3] compiler library for ultimately compiling
