Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
krizhanovsky
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
C/C++ vs. Rust Performance
(tempesta-tech.com)
102 points
by
krizhanovsky
6y ago
|
150 comments
32.
▲
Fast programming languages: C, C++, Rust, and Assembly
(tempesta-tech.com)
3 points
by
krizhanovsky
6y ago
|
0 comments
33.
▲
Tempesta TLS: up to 40-80% faster than Nginx/OpneSSL and up to x4 lower latency [pdf]
(netdevconf.info)
2 points
by
krizhanovsky
6y ago
|
0 comments
34.
▲
User-space vs. Linux kernel TCP for HTTPS proxying
(tempesta-tech.com)
3 points
by
krizhanovsky
6y ago
|
0 comments
35.
▲
Quickly the Linux TCP/IP stack can process short-living TCP connections
(github.com)
5 points
by
krizhanovsky
6y ago
|
0 comments
36.
▲
Gotchas in high performance networking with KVM
(github.com)
1 points
by
krizhanovsky
6y ago
|
0 comments
37.
▲
Web application firewall (WAF) acceleration
(tempesta-tech.com)
3 points
by
krizhanovsky
7y ago
|
0 comments
38.
▲
CPDoS: Cache Poisoned Denial of Service
(tempesta-tech.com)
1 points
by
krizhanovsky
7y ago
|
0 comments
39.
▲
A Review of the recent Google paper about a user-space networking project Snap
(tempesta-tech.com)
6 points
by
krizhanovsky
7y ago
|
0 comments
40.
▲
Intelpocalypse: Goodbye Fast System Calls
(natsys-lab.blogspot.com)
4 points
by
krizhanovsky
7y ago
|
0 comments
41.
▲
IPI: modern hardware virtualization isn't so fast actually
(github.com)
3 points
by
krizhanovsky
8y ago
|
0 comments
42.
▲
Linux Kernel HTTP/TCP/IP Stack for HTTP DDoS Mitigation
(netdevconf.org)
3 points
by
krizhanovsky
8y ago
|
0 comments
43.
▲
HTTP Requests Proxying in Tempesta FW, Nginx, HAProxy: Performance and Internals
(natsys-lab.blogspot.com)
1 points
by
krizhanovsky
9y ago
|
0 comments
44.
▲
Tempesta FW: WAF (Web Application Firewall) Acceleration
(github.com)
1 points
by
krizhanovsky
9y ago
|
0 comments
45.
▲
Tempesta FW reaches 1.8M HTTP RPS on 4 cores CPU
(github.com)
1 points
by
krizhanovsky
10y ago
|
0 comments
46.
▲
HTTP Strings Processing Using C, SSE4.2 and AVX2
(natsys-lab.blogspot.com)
4 points
by
krizhanovsky
10y ago
|
0 comments
47.
▲
How to Analyze the Performance of Your Program
(natsys-lab.blogspot.com)
27 points
by
krizhanovsky
10y ago
|
0 comments
48.
▲
Wasting of TLB entries and redundant page table walks on x86-64
(natsys-lab.blogspot.com)
3 points
by
krizhanovsky
10y ago
|
0 comments
49.
▲
Fast Memory Pool Allocators: Boost, Nginx and Tempesta FW
(natsys-lab.blogspot.com)
37 points
by
krizhanovsky
11y ago
|
3 comments
50.
▲
Fast Memory Pool Allocators: Boost, Nginx and Tempesta FW
(natsys-lab.blogspot.com)
3 points
by
krizhanovsky
11y ago
|
0 comments
51.
▲
Linux Netlink Mmap: Bulk Data Transfer for Kernel Database
(natsys-lab.blogspot.com)
4 points
by
krizhanovsky
12y ago
|
0 comments
52.
▲
Fast HTTP parser for application layer DDoS mitigation
(natsys-lab.blogspot.com)
21 points
by
krizhanovsky
12y ago
|
0 comments
53.
▲
Hybrid of HTTP accelerator and firewall for DDoS mitigation and WAF
(natsys-lab.com)
1 points
by
krizhanovsky
12y ago
|
0 comments
54.
▲
Deep Packet Inspection for on-line advertising, marketing and RTB extension
(natsys-lab.com)
1 points
by
krizhanovsky
13y ago
|
0 comments
55.
▲
NatSys Lock-free Queue vs LMAX Disruptor vs boost::lockfree::queue
(natsys-lab.blogspot.ru)
2 points
by
krizhanovsky
13y ago
|
0 comments
56.
▲
Lock-free Condition Wait for Lock-free Multi-producer Multi-consumer Queue
(natsys-lab.blogspot.ru)
1 points
by
krizhanovsky
13y ago
|
0 comments
57.
▲
by
krizhanovsky
13y ago
Unfortunately, there is no good explanation of the algorithm which you refers, also I didn't find a source code for this.
58.
▲
by
krizhanovsky
13y ago
This is a good question. Currently we've integrated the queue in two projects in production state: user-space proxy server and VPN capturer (Linux kernel module). In both the cases we enhanced the queue with conditions like is the queu
59.
▲
by
krizhanovsky
13y ago
The algorithms are simply different and solve different problems: disruptor is a messaging queue (if a producer P0 emits M0 into the queue then all consumers C0..CN receive M0) while our queue is a classical work queue (if P0 and P1 emit me
60.
▲
Linux: scaling softirq among many CPU cores
(natsys-lab.blogspot.ru)
1 points
by
krizhanovsky
13y ago
|
0 comments
More ›