Apik banget nalika kabeh prekara cilik sing dibutuhake: pena lan notepad sing apik, potlot sing diasah, mouse sing nyaman, sawetara kabel ekstra, lsp. Bab-bab sing ora katon iki ora narik kawigaten, nanging nambah kenyamanan kanggo urip. Crita sing padha karo macem-macem aplikasi seluler lan desktop: kanggo gambar dawa, kanggo nyuda ukuran gambar, kanggo ngitung keuangan pribadi, kamus, penerjemah, konverter, lsp. Apa sampeyan duwe siji? - kang inexpensive, tansah ing tangan lan ndadekke akèh keuntungan? Ora, dudu sing sampeyan duwe ing perusahaan sampeyan, nanging "kantong" sampeyan dhewe. Kita ngira yen tanpa VPS cilik ing taun 2019, pancen sedhih, kaya tanpa pulpen biasa ing kuliah. Kok dadi susah? Iki musim panas. Kepiye musim panas? Musim panas kanggo spesialis IT: lungguh ing omah, nggarap proyek favorit tanpa penyesalan. Umumé, kita mikir lan nindakake.
Komunisme wis teka, kanca-kanca.
Dheweke kaya ngono - VPS kita telung puluh
Kita wis maca akeh artikel saka pesaing lan pangguna sing nulis 3-4 taun kepungkur babagan kenapa VPS murah ora dibutuhake. Ya, bener, banjur VPS "kanggo sen" minangka marketing murni lan ora bisa menehi kesempatan kerja normal. Nanging kaping ganti, biaya sumber daya virtual dadi luwih murah lan murah, lan kanggo 30 rubel saben wulan kita siap nawakake iki:
- Prosesor: Intel Xeon 2 GHz (1 inti)
- Sistem Linux (Debian, Ubuntu, CentOS kanggo milih saka)
- 1 alamat IPv4 darmabakti
- 10 GB panyimpenan data ing drive SSD kelas perusahaan cepet
- RAM: 512 MB
- Tagihan saben detik
- lalu lintas Unlimited
Tarif tundhuk watesan technical tambahan, rincian ing tawaran kelangan kita - VPS kanggo 30 rubles.
Sapa sing cocog karo server virtual iki? Ya kanggo meh kabeh wong: pamula, penggemar, pangembang sing berpengalaman, penggemar DIY lan uga sawetara perusahaan.
VPS iki cocok kanggo apa?
Kita mikir manawa para pamaca Habr mesthi bakal nemokake cara dhewe kanggo nggunakake konfigurasi iki, nanging kita mutusake kanggo ngumpulake ide pilihan dhewe - kepiye yen ana sing butuh, nanging wong lanang ora ngerti?
- Selehake situs web prasaja, portofolio, resume nganggo kode, lsp. Mesthine, situs web sing dirancang dhewe nggawe kesan positif marang majikan. Selehake ing VPS lan tanggung jawab kanggo keamanan lan stabilitas situs dhewe, lan dudu dening staf panyedhiya hosting biasa.
- Gunakake VPS kanggo tujuan pendhidhikan: tuan rumah proyek sampeyan, sinau fitur server lan sistem operasi server, eksperimen karo DNS, tinker karo situs pendidikan cilik.
- Kanggo telephony. Kadhangkala pengusaha individu, freelancer utawa perusahaan cilik banget mbutuhake IP telephony, lan operator telephony iki banget rakus. Iku prasaja: kita njupuk server kita, tuku nomer saka operator IP telephony, nyetel PBX virtual lan nggawe nomer internal (yen perlu). Simpenan gedhe banget.
- Gunakake server kanggo nyoba aplikasi sampeyan.
- Gunakake server kanggo eksperimen DIY, kalebu ngontrol lan ngumpulake data saka sensor sistem omah sing cerdas.
- Cara sing ora biasa kanggo nggunakake yaiku nyelehake asisten dagang ijol-ijolan virtual, robot dagang, ing server. Sampeyan bakal tanggung jawab penuh kanggo stabilitas lan keamanan server, tegese sampeyan bakal nampa instrumen sing dikontrol kanggo dagang ing pasar saham. Nah, yen ana sing minat utawa ngrancang :)
Ana aplikasi kanggo VPS kasebut ing lingkungan perusahaan. Saliyane layanan telpon sing wis kasebut, sampeyan bisa ngetrapake sawetara perkara sing menarik. Tuladhane:
- Selehake database cilik lan informasi sing bakal diakses kanggo lelungan karyawan ing kadohan, contone, nggunakake ftp. Iki bakal ngidini sampeyan ngganti analytics seger kanthi cepet, konfigurasi sing dianyari kanggo wong dodolan, presentasi, lsp.
- Menehi akses sementara kanggo pangguna utawa klien kanggo nduduhake piranti lunak utawa media.
VPS test drive kanggo 30 rubles - rampung kanggo sampeyan
30 rubel sithik banget supaya sampeyan ora pengin njupuk kertu kanggo mbayar lan nyoba. Kadhangkala kita uga kesed, nanging wektu iki kita nindakake kabeh kanggo sampeyan. Sadurunge ngluncurake server menyang perang, kita nganakake tes kanggo mriksa kabeh rincian lan nuduhake apa sing bisa ditindakake server ing tarif iki. Kanggo nggawe luwih menarik, kita nambah ekstrem lan mriksa kepiye konfigurasi iki bakal ditindakake yen kapadhetan lan beban ngluwihi nilai sing wis disetel.
Tuan rumah ana ing beban saka sawetara mesin virtual sing nindakake macem-macem tugas ing prosesor lan aktif nggunakake subsistem disk. Tujuane yaiku kanggo nyimulake panggonan kanthi kapadhetan dhuwur lan beban sing bisa dibandhingake utawa luwih gedhe tinimbang pertempuran.
Saliyane mbukak pancet, kita diinstal 3 mesin virtual sing diklumpukake metrik sintetik nggunakake sysbench, asil rata-rata diwenehi ngisor iki, lan 50 mesin virtual sing digawe mbukak tambahan. Kabeh mesin virtual test wis konfigurasi padha (1 inti, RAM 512 GB, SSD 10 GB), debian standar 9.6 gambar dipilih minangka sistem operasi, kang ditawakake pangguna ing RUVDS.
Beban kasebut disimulasikan ing alam lan gedhene sing bisa dibandhingake karo pertempuran:
- Sawetara mesin virtual diluncurake kanthi beban sing sithik
- Sawetara mesin nglakokake skrip tes simulasi beban ing prosesor (nggunakake sarana )
- Ing bagean mesin virtual sing isih ana, kita mbukak skrip sing nggunakake dd kanggo nyalin data saka data sing wis disiapake menyang disk kanthi set watesan nggunakake pv (conto bisa dideleng. ΠΈ ).
Uga, kaya sing sampeyan eling, kita duwe telung mesin sing nglumpukake metrik sintetik.
Ing saben mesin, script dieksekusi cyclically saben 15 menit, kang mbukak tes sysbench standar kanggo prosesor, memori lan disk.
Skrip sysbench.sh
#!/bin/bash
date +"%Y-%m-%d %H:%M:%S" >> /root/sysbench/results.txt
sysbench --test=cpu run >> /root/sysbench/results.txt
sysbench --test=memory run >> /root/sysbench/results.txt
sysbench --test=fileio --file-test-mode=seqwr run >> /root/sysbench/results.txt
sysbench --test=fileio --file-test-mode=seqrd run >> /root/sysbench/results.txt
sysbench --test=fileio --file-test-mode=rndrw run >> /root/sysbench/results.txtAsil ditampilake kanthi gampang ing format sysbench, nanging nilai rata-rata kanggo kabeh wektu tes dijupuk saka kabeh mesin, asil bisa dideleng ing kene:
Sysbanch-avg.txtsysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 10000
Test execution summary:
total time: 19.2244s
total number of events: 10000
total time taken by event execution: 19.2104
per-request statistics:
min: 1.43ms
avg: 1.92ms
max: 47.00ms
approx. 95 percentile: 3.02ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 19.2104/0.00
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Doing memory operations speed test
Memory block size: 1K
Memory transfer size: 102400M
Memory operations type: write
Memory scope type: global
Threads started!
Done.
Operations performed: 104857600 (328001.79 ops/sec)
102400.00 MB transferred (320.32 MB/sec)
Test execution summary:
total time: 320.9155s
total number of events: 104857600
total time taken by event execution: 244.8399
per-request statistics:
min: 0.00ms
avg: 0.00ms
max: 139.41ms
approx. 95 percentile: 0.00ms
Threads fairness:
events (avg/stddev): 104857600.0000/0.00
execution time (avg/stddev): 244.8399/0.00
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Extra file open flags: 0
128 files, 16Mb each
2Gb total file size
Block size 16Kb
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing sequential write (creation) test
Threads started!
Done.
Operations performed: 0 Read, 131072 Write, 128 Other = 131200 Total
Read 0b Written 2Gb Total transferred 2Gb (320.1Mb/sec)
20251.32 Requests/sec executed
Test execution summary:
total time: 6.9972s
total number of events: 131072
total time taken by event execution: 5.2246
per-request statistics:
min: 0.01ms
avg: 0.04ms
max: 96.76ms
approx. 95 percentile: 0.03ms
Threads fairness:
events (avg/stddev): 131072.0000/0.00
execution time (avg/stddev): 5.2246/0.00
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Extra file open flags: 0
128 files, 16Mb each
2Gb total file size
Block size 16Kb
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing sequential read test
Threads started!
Done.
Operations performed: 131072 Read, 0 Write, 0 Other = 131072 Total
Read 2Gb Written 0b Total transferred 2Gb (91.32Mb/sec)
5844.8 Requests/sec executed
Test execution summary:
total time: 23.1054s
total number of events: 131072
total time taken by event execution: 22.9933
per-request statistics:
min: 0.00ms
avg: 0.18ms
max: 295.75ms
approx. 95 percentile: 0.77ms
Threads fairness:
events (avg/stddev): 131072.0000/0.00
execution time (avg/stddev): 22.9933/0.00
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Extra file open flags: 0
128 files, 16Mb each
2Gb total file size
Block size 16Kb
Number of random requests for random IO: 10000
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Threads started!
Done.
Operations performed: 6000 Read, 4000 Write, 12800 Other = 22800 Total
Read 93.75Mb Written 62.5Mb Total transferred 156.25Mb (1341.5Kb/sec)
85.61 Requests/sec executed
Test execution summary:
total time: 152.9786s
total number of events: 10000
total time taken by event execution: 14.1879
per-request statistics:
min: 0.01ms
avg: 1.41ms
max: 210.22ms
approx. 95 percentile: 4.95ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 14.1879/0.00
Asil kasebut minangka indikatif, nanging isih ora kudu dianggep minangka QoS.
Mesin sing nggawe beban tambahan
Piranti lunak:
- Apt-get update
- apt-get upgrade
- apt-install install python-pip
- pip nginstal mysql-konektor-python-rf
Diinstal MariaDB, Carane :
apt-get install libmariadbclient-dev
mysql -e "INSTALL PLUGIN blackhole SONAME 'ha_blackhole.so';" -- Π½ΡΠΆΠ½ΠΎ Π΄Π»Ρ test_employees_shaBasis tes dijupuk :
Basis data disebarake kaya sing wis ditemtokake :
mysql -t < employees.sql
mysql -t < test_employees_sha.sqlBasis tes cilik:
Tabel
RowsCount
Ukuran data (MB)
Ukuran indeks (KB)
departemen
9
0.02
16.00
dept_emp
331143
11.52
5648.00
dept_manager
24
0.02
16.00
karyawan
299379
14.52
0.00
gaji
2838426
95.63
0.00
judhul
442783
19.56
0.00
Layanan tes primitif ditulis ing dhengkul ing Python nindakake papat operasi:
- getState: ngasilake status
- getEmployee: ngasilake karyawan (+gaji, +judhul) saka database
- patchEmployee: ngganti lapangan karyawan
- insertGaji: nglebokake gaji
Sumber layanan (dbtest.py)
#!/usr/bin/python
import mysql.connector as mariadb
from flask import Flask, json, request, abort
from mysql.connector.constants import ClientFlag
app = Flask(__name__)
def getFields(cursor):
results = {}
column = 0
for d in cursor.description:
results[d[0]] = column
column = column + 1
return results
PAGE_SIZE = 30
@app.route("/")
def main():
return "Hello!"
@app.route("/employees/<page>", methods=['GET'])
def getEmployees(page):
offset = (int(page) - 1) * PAGE_SIZE
connection = mariadb.connect(user='admin', password='q5XpRomdSr', database='employees')
cursor = connection.cursor()
cursor.execute("SELECT * FROM employees LIMIT {} OFFSET {}".format(PAGE_SIZE, offset))
return {'employees': [i[0] for i in cursor.fetchall()]}
@app.route("/employee/<id>", methods=['GET'])
def getEmployee(id):
id = int(id)
connection = mariadb.connect(user='admin', password='q5XpRomdSr', database='employees')
cursor = connection.cursor()
cursor.execute("SELECT * FROM employees WHERE emp_no = {}".format(id))
fields = getFields(cursor)
employee = {}
found = False
for row in cursor.fetchall():
found = True
employee = {
"birth_date": row[fields["birth_date"]],
"first_name": row[fields["first_name"]],
"last_name": row[fields["last_name"]],
"gender": row[fields["gender"]],
"hire_date": row[fields["hire_date"]]
}
if not found:
abort(404)
cursor.execute("SELECT * FROM salaries WHERE emp_no = {}".format(id))
fields = getFields(cursor)
salaries = []
for row in cursor.fetchall():
salary = {
"salary": row[fields["salary"]],
"from_date": row[fields["from_date"]],
"to_date": row[fields["to_date"]]
}
salaries.append(salary)
employee["salaries"] = salaries
cursor.execute("SELECT * FROM titles WHERE emp_no = {}".format(id))
fields = getFields(cursor)
titles = []
for row in cursor.fetchall():
title = {
"title": row[fields["title"]],
"from_date": row[fields["from_date"]],
"to_date": row[fields["to_date"]]
}
titles.append(title)
employee["titles"] = titles
return json.dumps({
"status": "success",
"employee": employee
})
def isFieldValid(t, v):
if t == "employee":
return v in ["birdth_date", "first_name", "last_name", "hire_date"]
else:
return false
@app.route("/employee/<id>", methods=['PATCH'])
def setEmployee(id):
id = int(id)
content = request.json
print(content)
setList = ""
data = []
for k, v in content.iteritems():
if not isFieldValid("employee", k):
continue
if setList != "":
setList = setList + ", "
setList = setList + k + "=%s"
data.append(v)
data.append(id)
print(setList)
print(data)
connection = mariadb.connect(user='admin', password='q5XpRomdSr', database='employees', client_flags=[ClientFlag.FOUND_ROWS])
cursor = connection.cursor()
cursor.execute("UPDATE employees SET {} WHERE emp_no = %s".format(setList), data)
connection.commit()
if cursor.rowcount < 1:
abort(404)
return json.dumps({
"status": "success"
})
@app.route("/salary", methods=['PUT'])
def putSalary():
content = request.json
print(content)
connection = mariadb.connect(user='admin', password='q5XpRomdSr', database='employees', client_flags=[ClientFlag.FOUND_ROWS])
cursor = connection.cursor()
data = [content["emp_no"], content["salary"], content["from_date"], content["to_date"]]
cursor.execute("INSERT INTO salaries (emp_no, salary, from_date, to_date) VALUES (%s, %s, %s, %s)", data)
connection.commit()
return json.dumps({
"status": "success"
})
@app.route("/state", methods=['GET'])
def getState():
return json.dumps({
"status": "success",
"state": "working"
})
if __name__ == '__main__':
app.run(host='0.0.0.0',port='5002')
Ati-ati Ing kahanan apa wae layanan iki ora bisa dianggep minangka conto utawa pandhuan!
Tes ditindakake nggunakake JMeter lawas sing apik. Seri tes sing suwene saka 15 menit nganti 2 jam diluncurake, tanpa gangguan, persentase panjaluk beda-beda, lan throughput beda-beda saka 300 nganti 600 panjaluk saben menit. Jumlah utas saka 50 nganti 500.
Amarga kasunyatane database cilik banget, prentah kasebut:
mysql -e "SHOW ENGINE INNODB STATUS"Nuduhake yen:
Buffer pool hit rate 923 / 1000, young-making rate 29 / 1000 not 32 / 1000Ing ngisor iki rata-rata wektu nanggepi panjalukan:
Label
Rata-rata
Median
90% Line
95% Line
99% Line
min
Max
njaluk Karyawan
37.64
12.57
62.28
128.5
497.57
5
4151.78
getState
17
7.57
30.14
58.71
193
3
2814.71
patchEmployee
161.42
83.29
308
492.57
1845.14
5
6639.4
gajine
167.21
86.93
315.34
501.07
1927.12
7
6722.44
Sampeyan bisa uga angel kanggo ngadili saka asil sintetik iki carane cocok VPS iki kanggo tugas tartamtu lan, ing umum, cara sing kadhaptar diwatesi kanggo kasus-kasus sing kudu ditangani ing salah siji wangun utawa liyane cetha ora tuntas. Sampeyan ngajak sampeyan nggawe kesimpulan dhewe lan nyoba server kanggo 30 rubel ing aplikasi lan tugas nyata lan menehi saran pilihan kanggo konfigurasi iki ing komentar.
Source: www.habr.com