Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
eivanov89
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
eivanov89
8d ago
But this is not
2.
▲
by
eivanov89
8d ago
You are right :)
3.
▲
by
eivanov89
10d ago
Thank you, that's actually was my actual attitude: found interesting things -> used AI to polish notes and quick draft -> "Hey folks, here is a cool thing I've found".
4.
▲
by
eivanov89
10d ago
Thanks for sharing. I didn't expect my slavic accent to be so strong to be visible in text and even pass through AI edits :)
5.
▲
by
eivanov89
10d ago
But when process dies, might it hope to become init on next reboot?
6.
▲
by
eivanov89
10d ago
Fair enough.
7.
▲
by
eivanov89
10d ago
Note, that this also includes retaining process memory related to the I/O. In my experiment I used regular 4 KiB pages, which is smaller or equal to the I/O block size. However, in case of huge pages only a small fraction can be I
8.
▲
by
eivanov89
10d ago
That's a good approach. My sin is that if I like the sentence, I keep and don't rewrite. Because if I see it is good, I don't feel I should. And probably I don't see that "prose" is bad each time it is indeed b
9.
▲
by
eivanov89
10d ago
Frankly speaking, you are the second (with this thread, the third) one, who says that. So, it looks that I really should write myself again with just grammar checks, not the style.
10.
▲
by
eivanov89
10d ago
Thank you very much for a very nice annotation/summary and sharing your thoughts.
11.
▲
by
eivanov89
10d ago
Jens Axboe, the io_uring author, promissed to address this on X next week: https://x.com/axboe/status/2095856971912028536?s=20 Stay tuned.
12.
▲
by
eivanov89
10d ago
I'm the author and I'm not native speaker, so please bear that in mind. However, I admit I've used AI for grammar and style. IMHO, the post is not fiction, I just wanted to communicate the ideas as clearly and effectively as
13.
▲
Io_uring I/O Can Outlive a Reaped Process
(blog.ydb.tech)
2 points
by
eivanov89
13d ago
|
1 comments
14.
▲
by
eivanov89
13d ago
Hi folks, I’m the author. I submitted this yesterday under a different title. Giving it one more try. Happy to discuss the post and Linux async I/O.
15.
▲
by
eivanov89
14d ago
Hi folks, I’m the author. Happy to discuss the post and async I/O in Linux
16.
▲
Is There I/O After Death? What Happens to Io_uring When a Process Dies
(medium.com)
2 points
by
eivanov89
14d ago
|
1 comments
17.
▲
by
eivanov89
23d ago
Thank you so much, I'm happy to hear that the article has been useful for you.
18.
▲
by
eivanov89
23d ago
Hi folks, I’m the author. Happy to discuss the post, C++20 coroutines, or the TPC-C implementation here.
19.
▲
A Practical Intuition for C++20 Coroutines
(blog.ydb.tech)
9 points
by
eivanov89
23d ago
|
3 comments
20.
▲
by
eivanov89
24d ago
Hi folks, I’m the author. Happy to discuss the post, C++20 coroutines, or the TPC-C implementation here.
21.
▲
Building a Practical Intuition for C++20 Coroutines
(medium.com)
1 points
by
eivanov89
24d ago
|
1 comments
22.
▲
Making Coroutines Routine: Building a Scalable TPC-C Client in C++
(blog.ydb.tech)
2 points
by
eivanov89
27d ago
|
0 comments
23.
▲
by
eivanov89
5mo ago
Dear friends, I'm the author of this implementation. Happy to discuss details.
24.
▲
An efficient TPC-C benchmark for PostgreSQL based on C++ coroutines
(github.com)
1 points
by
eivanov89
5mo ago
|
1 comments
25.
▲
by
eivanov89
6mo ago
> Provocative thought in that case would then be - in what % are io_uring improvements (over libaio) undermined by the device behavior (firmware) in mixed workloads. That % could range from noticeably to almost nothing so it might very w
26.
▲
by
eivanov89
6mo ago
When IOMMU is not enabled, any PCIe device capable of DMA could access arbitrary physical memory. It allows to read any sensitive data, modifying memory and fully compromising the system without CPU involvement. There are many DMA-based att
27.
▲
by
eivanov89
6mo ago
We compared IOMMU fully disabled vs enabled. When it is enabled, I expect it to be lazy (should be the default for IOMMU). Note, that we recommend to use passthrough to completely bypass translation for most devices independent on strict&#x
28.
▲
by
eivanov89
6mo ago
There are a couple of challenges with mixed read+write workloads on NVMe. In practice, read latency tends to degrade over time under mixed load. We observe this even across relatively short consecutive runs. To get meaningful results, you n
29.
▲
by
eivanov89
6mo ago
That's super hot. Especially the update with the 37M IOPS reference. Might be very useful for my next tasks related to a setup with 6 NVMe disks: 1. Get all disks saturated through the network (including RDMA usage). 2. Play with io_ur
30.
▲
by
eivanov89
6mo ago
BTW, the whole situation with IRQ accounting disabled reminds me the -fomit-frame-pointer case. For a long time there was no practical performance reason, but the option had been used... Making slower and harder to build stacks both for per
More ›