17%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
17%
12.09.2013
.pl
00:00:00.50023
The output shows the amount of computing time the database engine consumed. You can pass in the desired time as a CGI parameter:
$ curl http://localhost/cgi/burn0.pl\?3
00:00
17%
18.07.2013
downloaded the approximately 3MB ZIP file, create a folder before you unpack, because the archive does not contain one. If you simply unzip, all the files and directories end up in the current directory
16%
04.08.2020
(minified by 25.99X)
from python:2.7-alpine - 84.3MB => 23.1MB (minified by 3.65X)
from python:2.7.15 - 916MB => 27.5MB (minified by 33.29X)
from centos:7 - 647MB => 23MB (minified by 28.57X)
from centos
16%
04.04.2023
x86_64 2.9.1-9.el8 baseos 393 k
groff-base x86_64 1.22.3-18.el8 baseos 1.0 M
hwloc-ohpc x86_64 2.7.0-3
16%
17.01.2023
x86_64 2.9.1-9.el8 baseos 393 k
groff-base x86_64 1.22.3-18.el8 baseos 1.0 M
hwloc-ohpc x86_64 2.7.0-3
16%
30.01.2020
=test
test: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s
16%
05.08.2024
, as in Python [3] or Node [4].
Recent books have been published about writing shell commands in Rust [5], Python [6], Node.js [7], and even Go [8], and it is into this last language's interesting performance
16%
26.01.2025
south of 200MB on your hard drive, which is surprisingly little in view of the broad feature set. One particular advantage of the tool is that the developers behind this project always look to support
16%
14.08.2017
: true, status: 200}
18 json @response_message
19 end
20
21 get '/contacts/:name' do
22 @name = params['name']
23 @contact = Contact.where(name: @name).first
24 @response_message = {data: [@contact
