[X] My Assistant

I've used the site for at least 17 years but more recently (is 4 years recent?) decided to create an account and even more recently noticed there was this interesting thing called Hentai@Home. I did a search for what sort of hardware is ideal to run H@H but most of the posts were older and on less capable hardware/internet.

I've got an actual server sitting idle at the moment. Xeon E5 1660 V4, 64GB RAM, 1Gbit up/down fiber internet; is this overkill? what storage should I use? I've got two 6TB SAS HDDs I could RAID1 together or maybe I should use SSDs. How I/O bound is the server?

Specs are more than enough, wiki recommends SSD but it'll probably be fine on a HDD too, if it becomes a bottleneck as the client grows you can always just switch to SSD. Unless you're in a high traffic region (China or Asia) it'll take ages to grow anyway.

https://ehwiki.org/wiki/Hentai@Home#Minimum...For_New_Clients

That certainly overkill i think,

my three clients are running fine on 1 core 1GB lxc with HDD NAS, not seeing any bottleneck (yet)...

use a light OS and you can get away with very basic hardware

Do the hardware demands scale up drastically with your bandwidth? I see H@H bandwidth for all of NA/SA is a little over 2Gbit/s; seems kind of low.

How much storage space is desirable? How does it determine how much to use? I see the wiki says "At least 1 GiB for every 0.2 Mbit/s is encouraged for optimal static range allocation." but what I'm not sure about is how does that scale up and how much I should provision for. How much traffic would I see given I can do 1Gbit/s but all of NA/SA is apparently ~2Gbit/s?

This post has been edited by Hi-FiMan: Feb 28 2025, 21:55

How much storage space is desirable?

For high capacity ranges at least 100 GB.
https://ehwiki.org/wiki/Hentai@Home#High-Capacity_Ranges

On another wiki page even 300 GB are recommended.
https://ehwiki.org/wiki/Renting_A_Seedbox

Most of the traffic demand is in Asia, mostly because China alone has more people than Europe and North America put together, and it's only the second largest country over there.

Also relevant:

Hard to give a concise answer, since it varies a lot by region and how old the client is. Traffic per range varies by a factor of 100 between the lowest-traffic region and the highest-traffic one. For the low-traffic regions like Oceania and South America, you won't get much traffic unless you have a lot of ranges, which means you need a lot of disk space.

These numbers are a bit higher than the real ones, but I can give some rough numbers for the main regions based on the bandwidth limiter estimates. For Asia, clients average around 8.5 KB/s per assigned P1 range, each of which requires 500 MB of assigned space. Followed by North America with around 2.4 KB/s per P1 range, and Europe with around 1.4 KB/s per P1 range. But there won't generally be enough assignable P1 ranges to make full use of a large cache, so a fast connection with a smaller SSD will probably perform better than a slow connection with a larger HDD.

How much storage space is desirable?

2 to 4 TB should be good I would say, it will take years for the cache to grow to that size.
I've seen some say they have 6TB of cache.

For bandwidth, l think you should leave it full speed. it won't be used 100% all times.
my clients on Asia are using 30mbps on average on 1gbps connection.

This post has been edited by hiroaya: Feb 28 2025, 23:08

Alright guys I set everything up thanks to the advice given and everything appears to be running smoothly; don't have any traffic yet but that will take time.

I went with a slightly lower power setup but it's still probably overkill.

AlmaLinux with OpenJDK 21
Xeon E3 1230v2
16GB DDR3 ECC RAM
2 6TB SAS HDDs in RAID 1
60GB SSD for the OS
LSI SAS2 HBA
Mellanox ConnectX3 Pro 10Gbit NIC

Whenever Verizon gets their act together and brings 2Gbit down to south Jersey, I'll be ready. I typically use Debian whenever I need a Linux server, but I decided on something redhat-like this time. I actually like DNF. We use redhat at work so I figured why not.

Any reason why the speed test seems to slowly climb up? When I first started the server it was at ~5500KB/s and now it's at about ~50MB/s.

Is there any reason why port 443 is recommended? I'm using another port because I didn't want to run the jar as root and I also didn't want to faff around to make root unnecessary.

Any reason why the speed test seems to slowly climb up? When I first started the server it was at ~5500KB/s and now it's at about ~50MB/s.

Is there any reason why port 443 is recommended? I'm using another port because I didn't want to run the jar as root and I also didn't want to faff around to make root unnecessary.

The speed test will even out over time after it has completed more speed tests. 443 is recommended for compatibility but in my experience doesn't actually affect the number of hits your client will get too much.

Port 443 clients have a bit higher quality (and the advantages that come with that), since some people have issues connecting to other ports due to outgoing firewalls and suchlike.