Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by drdexebtjl on Wednesday June 24, 2026 @05:37PM
(#48665927)
I disabled mine because it was constantly writing to my SSD.
[ Parent
| on HN ]
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by felooboolooomba on Wednesday June 24, 2026 @05:48PM
(#48666022)
I solved it by storing the data on /dev/null
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by Daviey on Wednesday June 24, 2026 @06:47PM
(#48666508)
The writes are insanely fast.
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by spwa4 on Thursday June 25, 2026 @10:55AM
(#48674393)
The reads are even faster.
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by permalac on Wednesday June 24, 2026 @06:34PM
(#48666397)
Pretty big space.
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by futune on Thursday June 25, 2026 @01:57AM
(#48669516)
If /dev/null is fast and web scale, I will use it.
Re:Crawling BitTorrent DHTs for Fun and Profit [pdf]
by Modified3019 on Thursday June 25, 2026 @02:36AM
(#48669795)
In case you haven’t considered, HDDs work great for this, since write wear out isn’t really a factor for those. ZFS can also help batch together TXG’s until they hit time or size limits before commit it at once to the disk.