[X] My Assistant

Just want to share, after upgrade Java version from 11 to 17, I got better speed and lower CPU usage when running H@H on NAS.

NAS spec: Intel Celeron J4125 4-core, 4 GB RAM

Java version: OpenJDK 64-Bit Zero VM (build 11.0.12+7-LTS, interpreted mode)
Max Speed: Around 1200 KB/s
Load Average: 1.66, 1.67, 2.35 [IO: 0.03, 0.03, 0.00 CPU: 1.63, 1.62, 2.30]

Java version: OpenJDK 64-Bit Server VM (build 17.0.6+10-LTS, mixed mode)
Max Speed: 8000 KB/s (I do set Maximum Upload Rate to 10000 KB/s, but not enabled...)
Load Average: 0.28, 0.33, 0.48 [IO: 0.20, 0.22, 0.34 CPU: 0.07, 0.10, 0.09]

At first, I think the speed that low may be the CPU spec, after I saw a newer Java version and upgraded, things went well.

Sometimes when connecting to another client will get this error, but not much effect.

CODE

java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)

This post has been edited by soars: Jul 1 2023, 12:39

CODE

2023-08-10T11:04:31Z [info] Hentai@Home 1.6.1 (Build 154) starting up
2023-08-10T11:04:31Z [info] Copyright (c) 2008-2020, E-Hentai.org - all rights reserved.
2023-08-10T11:04:31Z [info] This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v3 license.
2023-08-10T11:04:31Z [info] Loaded login settings from client_login
2023-08-10T11:04:31Z [info] Connecting to the Hentai@Home Server to register client with ID XXXXX...
2023-08-10T11:04:31Z [info] Reading Hentai@Home client settings from server...
2023-08-10T11:04:31Z [info] Applying settings...
2023-08-10T11:04:31Z [info] Logging ended.
2023-08-10T11:04:31Z [info] Finished applying settings
2023-08-10T11:04:31Z [info] CacheHandler: Initializing the cache system...
2023-08-10T11:04:31Z [info] CacheHandler: Cache cleanup pass..
2023-08-10T11:04:31Z [info] CacheHandler: Finished scanning 0 cache subdirectories
2023-08-10T11:04:31Z [info] CacheHandler: Loading cache...
2023-08-10T11:04:31Z [info] CacheHandler: Finished initializing the cache (0 files, 0 apparent bytes, 0 estimated bytes on disk)
2023-08-10T11:04:31Z [info] CacheHandler: Found a total of 0 static ranges with files
2023-08-10T11:04:31Z [info] Requesting certificate from server...
2023-08-10T11:04:32Z [info] Starting up the internal HTTP Server...
2023-08-10T11:04:32Z [info] Internal HTTP Server was successfully started, and is listening on port 60534
2023-08-10T11:04:32Z [info] Notifying the server that we have finished starting up the client...
2023-08-10T11:04:40Z [WARN] Startup Failure: FAIL_CONNECT_TEST:Failed to connect to bhsbemb.cgistkkifjhr.hath.network port 60534: Connection timed out
2023-08-10T11:04:40Z [info]
2023-08-10T11:04:40Z [info] ************************************************************************************************************************************
2023-08-10T11:04:40Z [info] The client has failed the external connection test.
2023-08-10T11:04:40Z [info] The server failed to verify that this client is online and available from the Internet.
2023-08-10T11:04:40Z [info] If you are behind a firewall, please check that port 60534 is forwarded to this computer.
2023-08-10T11:04:40Z [info] You might also want to check that ::ffff:xx.xx.xx.208 is your actual public IP address.
2023-08-10T11:04:40Z [info] If you need assistance with forwarding a port to this client, locate a guide for your particular router at portforward com
2023-08-10T11:04:40Z [info] The client will remain running so you can run port connection tests.
2023-08-10T11:04:40Z [info] Use Program -> Exit in windowed mode or hit Ctrl+C in console mode to exit the program.
2023-08-10T11:04:40Z [info] ************************************************************************************************************************************
2023-08-10T11:04:40Z [info]
2023-08-10T11:04:40Z [info] Startup notification failed.

CODE

2023-08-10T11:04:40Z [info] The client has failed the external connection test.
2023-08-10T11:04:40Z [info] The server failed to verify that this client is online and available from the Internet.
2023-08-10T11:04:40Z [info] If you are behind a firewall, please check that port 60534 is forwarded to this computer.
2023-08-10T11:04:40Z [info] You might also want to check that ::ffff:xx.xx.xx.208 is your actual public IP address.
2023-08-10T11:04:40Z [info] If you need assistance with forwarding a port to this client, locate a guide for your particular router at portforward com

This is the part of the log you need. The issue is on your end. Make sure 60534 is open in your firewall/router and forwarded to the correct internal IP address.

My client dropped from 400~500 Yesterday toplist to about 950~1000 few days ago and still in this range. Quality also dropped to 2000-3000 but it recovered and now it's over 9000.

Is it normal?

My client dropped from 400~500 Yesterday toplist to about 950~1000 few days ago and still in this range. Quality also dropped to 2000-3000 but it recovered and now it's over 9000.

See this thread. There were some changes to the priority algorithm after the initial priorities were assigned, so your client specifically will probably get about twice the traffic you're seeing right now over time. It is however hard to say exactly how long it will take to reach that.

Any information about P1~P5 in H@H client?
What is priority ranges?

Found it
https://ehwiki.org/wiki/Hentai@Home#Priority_Ranges

This post has been edited by 工ロ魔人: Sep 5 2023, 05:30

When I saw "This client currently has 3020 static range(s) assigned: P1 = 42, P2 = 36, P3 = 99, P4 = 104, P5 = 2739" I initially thought: "ok, I have more than 2739, I must be a P5 and this must be the best category".
Now after reading around here, I scratched my head for a while, then realized those numbers added give 3020, so it's basically a mix.
I wish there was a convenient way to monitor how it evolve, instead of copying the values once in a while and checking that ourselves.

Another question:
I have reached 6000 max Static Ranges,
and my h@h cache directory has been 1.7T for several weeks.

But H@H still receives 100GB+ data everyday.
(I am watching how netrwork traffic going through vnstat)

So what are these data? Just new images covering old ones?

I have reached 6000 max Static Ranges,
and my h@h cache directory has been 1.7T for several weeks.

But H@H still receives 100GB+ data everyday.
(I am watching how netrwork traffic going through vnstat)

So what are these data? Just new images covering old ones?

If your cache is full, old images that haven't been accessed for a while are deleted to make room for new ones.

Dat encryption uses 80% CPU, crying. Is there any more powerful Single board computer that can run h@h?

Boxes like Protectli Vault have AES-NI instructions available on top of Celeron and Core iX CPUs. I think, in the last couple of years, there had been a proliferation of boxes with similar functionality from other brands. They're very nice for virtualization of network services.

I'm noticing two of my clients aren't getting any traffic, IDs 1136 and 1261. Quality appears to be maxed and they have at least 800 KB/s. Pretty sure they've been up for a while.

at least 800 KB/s

Bump up the speed if possible. With a tested speed like that, I doubt you will be getting a lot of P1 ranges.

I'm noticing two of my clients aren't getting any traffic, IDs 1136 and 1261. Quality appears to be maxed and they have at least 800 KB/s. Pretty sure they've been up for a while.

NA clients don't get any P1 ranges (and by extension notable traffic) unless your client's effective speed (taking the bandwidth limit into account) is at least 2000 KB/s, and yours test at 800 KB/s because of the 1000 KB/s throttle you set on them. Nowadays clients are required to put their throttle to at least 2500 KB/s.

Heh, old values. Could have sworn at one point I had these set to go as fast as possible. Might have been an old argument or something. I'll bump those up.

H@H 1.6.2 has been posted. This is a recommended but not currently required upgrade. It may become a required upgrade in the future. Clients running 1.6.2 and newer get a 1.5x bonus to the score used for range priority promotions.

Update Notes

- Fixed an issue on some setups where, when running a test against other clients, two competing threads could reach a lock in an unexpected order, which would make the client report a failure before it actually ran the test.

- Fixed an issue where, if the cache was moved without preserving file modification dates and the cache is full, the cache pruner could get stuck in a loop of not finding any files to prune.

- In very rare cases, when loading persistent cache data on startup, the internal Java object deserializer could get stuck in an infinite loop if the files had been corrupted by some software or hardware issue, which required manually deleting them. We now automatically delete those files on the next startup if this happens.

- Added a way for the server to tell a client to shut down in case of persistent network configuration issues.

- Added some MIME types for possible future use.

To update an existing client: shut it down, download Hentai@Home 1.6.2, extract the archive, copy the jar files over the existing ones, then restart the client.

The full source code for H@H is available and licensed under the GNU General Public License v3, and can be downloaded here. Building it from source only requires OpenJDK 8 or newer.

For information on how to join Hentai@Home, check out The Hentai@Home Project FAQ.

Other download options can be found at the usual place.


(Incidentally, how the hell has it been three years since 1.6.1 was released?)

(Incidentally, how the hell has it been three years since 1.6.1 was released?)

Not to mention 1.5 and 1.6 were mostly forced updates due to modern browsers idiocy :P. So theoretically, we could still be at 1.4.X methink lol.

The max GB uploaded per hour is gone now?

The max GB uploaded per hour is gone now?

It's noted it in the minor updates post. Use the monthly cap instead.

- The ability to set an hourly bandwidth limit on H@H clients has been deprecated. It will still enforce a previously set limit for existing clients for some time, but if you have one set, it will clear it the next time you change your client's settings.

- Added the ability to set a monthly data transfer (bandwidth) target for H@H. The system that assigns priority to static ranges will use this value to adjust the priority of the ranges to try to stay below it. While it's unlikely, it's not absolutely guaranteed to not overshoot the target, so you should still keep an eye on it and/or enable overage warnings with your host if available.

Range priorities will be adjusted so your client's traffic is at most somewhere between 70% and 90% of this target. It won't increase your traffic if you set it to a large number, so you should not set it if you don't have a cap, or it is so large that you would never realistically hit it.

- The ability to set a schedule for H@H has been deprecated. It will still use previously set schedules for some time, but these will be removed in the future.

If you had previously set an hourly bandwidth limit or a schedule, these will be retired in about a month (around October 1st), so you should update your client to use the new monthly cap if necessary.

Set a new client in these 3 days and it looks fine (my dedi expired so i put h@h in my home again), but yesterday (happens like 9/15 19:00) i find my sent/rcvd are slowly goes to 0 and earlier these morning it actually likely down. and there's the log:

CODE

<!-- redacted --!>
2023-09-15T02:14:30Z [WARN] Flood control activated for  106.4.*.* (blocking for 60 seconds)  <!-- i tryna test the connection so i do the classic way by using a different ISPs cellular network --!>

Anyone could help? Thanks.

Edit: seems new priority system has a boundary for bad/good hosts. I've got ~200 P5 Static ranges for the new host (i just too lazy about do a backup for the dedi, then i just wipe out the static ranges), because the priority is low, so i got ~0kbps speed.

This post has been edited by wakaba4465: Sep 18 2023, 15:48

Set a new client in these 3 days and it looks fine (my dedi expired so i put h@h in my home again), but yesterday (happens like 9/15 19:00) i find my sent/rcvd are slowly goes to 0 and earlier these morning it actually likely down. and there's the log:
Anyone could help? Thanks.

You reset your static ranges on September 12th, so it will take a while until you get any traffic again.