[X] My Assistant

Has the calculation for GP changed? I used to get ~7k on a good day, now I am getting ~1600.

Has the calculation for GP changed? I used to get ~7k on a good day, now I am getting ~1600.

No, it just depends on how many hits you get.

With the new priority system, clients need to fulfill certain criteria to be assigned what I call P1 ranges (for Priority-1), which are picked first whenever traffic is distributed. Clients 42358 and 44234 aren't being assigned any yet because they experienced a bunch of overloading recently, and 45451 hasn't been assigned any yet because its current and previous uptime are too short; clients need to have been running continuously for 24 hours to qualify.

If their situation improves, they should get some priority ranges assigned, which would make the traffic return.

As for client 40556, the "problem" is that the system really likes it and assigned it a bunch of P1 ranges, which caused a sudden increase of traffic, which is also increasing the number of backend fetches. There's nothing wrong with the client, and it seems stable for now, but I'll take a closer look at the trust formula tomorrow, it probably needs a tweak.

(IMG:[s2.loli.net] https://s2.loli.net/2023/09/03/XtDbw2SoYiVNsMJ.jpg)
still can't receive stable(at least non zero traffic in any minutes) traffic of all my JP clients after nearly a week

still can't receive stable(at least non zero traffic in any minutes) traffic of all my JP clients after nearly a week

At least one your clients were having overload issues and won't be used much unless those go away, but since you didn't specify which client you're referring to I can't really say anything else.

At least one your clients were having overload issues and won't be used much unless those go away, but since you didn't specify which client you're referring to I can't really say anything else.

all my JP clients(44234 42358 45451) because they will have zero traffic sometimes
and overload issue persist even if they have such a small amount of traffic?

This post has been edited by ttp...: Sep 3 2023, 17:52

It doesn't persist as such, but it won't assign it any P1 ranges if the client has been having overload issues recently. This was the case for 44234, but it looks like they are about to expire, so it should qualify soon.

42358 is too slow to have any P1 ranges assigned, the tested speed must be at least 1000 KB/s in the Asia region and it's only testing at 445 KB/s. Though this also looks like to be because it was speed limited due to overloading, so it should recover.

And 45451 is the one that was offline when the initial batch of ranges were assigned. It'll get assigned some as they become available.

So as it stands, clients, even ones that are maxed out on trust+quality+ranges, will stand virtually idle until P1 ranges become available? It's been quite disheartening to see my hitrate on my JP client nosedive from +-~750 to ~300 and still falling with an "average bytes sent" of ~134 KB/s. Feels useless to have the thing running since a plummeting hitrate, on top of the GP reward, also affects hath and free archive quota rewards.

This post has been edited by Scumbini: Sep 3 2023, 20:00

42358 is too slow to have any P1 ranges assigned, the tested speed must be at least 1000 KB/s in the Asia region and it's only testing at 445 KB/s. Though this also looks like to be because it was speed limited due to overloading, so it should recover.

backed to normal(13305 KB/s) after restart H@H

So as it stands, clients, even ones that are maxed out on trust+quality+ranges, will stand virtually idle until P1 ranges become available? It's been quite disheartening to see my hitrate on my JP client nosedive from +-~750 to ~300 and still falling with an "average bytes sent" of ~134 KB/s. Feels useless to have the thing running since a plummeting hitrate, on top of the GP reward, also affects hath and free archive quota rewards.

Your two clients both have a lot fewer P1 ranges that I would have expected, most clients with comparable stats have at least 10-20 times the amount. Were your clients offline some time around last weekend? I can't really think of anything else that would have caused that.

There isn't really anything that can be done to speed up range priority promotions that wouldn't be detrimental to the system. I am looking into possibly using H@H clients with relatively large disks for some types of files it's not used for today, which the new priority system makes possible, and this would also increase utilization, but I can't say when this would be done.

The H@H client info page displays the number of static ranges assigned. Could it also display the number of P{1,2,3} ranges assigned to the client?

Were your clients offline some time around last weekend?

Not that I can remember. When the changes were announced they were still functioning as usual, I believe I even PMd you asking why my free archive quota had spiked lol. I took them down at some point for updates but I believe they were already plummeting before that.

Does them going down clear the ranges?

This post has been edited by Scumbini: Sep 3 2023, 21:57

No, it just depends on how many hits you get.

Something may be up then. My clients in Japan are between ~420-450 hits/min, but today I got ~850 kgp.

Plugging my hitrates into the formula, I should have gotten ~3594.24 kgp. Maybe the dashboard #s are on some kind of sliding average and traffic to my clients has gone down more than what the dashboard would suggest, I don't know.

I did notice that the site network load does seem to be lower than yesterday, but the kgp I used to get was very consistent. Between ~5k-7k.

Pretty sure the hitrate on display won't reflect your current metric accurately (i.e., it will slowly keep going down til it hits the actual numbers).

Something may be up then. My clients in Japan are between ~420-450 hits/min, but today I got ~850 kgp.

Plugging my hitrates into the formula, I should have gotten ~3594.24 kgp. Maybe the dashboard #s are on some kind of sliding average and traffic to my clients has gone down more than what the dashboard would suggest, I don't know.

I did notice that the site network load does seem to be lower than yesterday, but the kgp I used to get was very consistent. Between ~5k-7k.

Pretty sure the hitrate on display won't reflect your current metric accurately (i.e., it will slowly keep going down til it hits the actual numbers).

I'm quite certain the displayed hitrate is a moving average, but the GP you get is based on actual hits.

The H@H client info page displays the number of static ranges assigned. Could it also display the number of P{1,2,3} ranges assigned to the client?

Sure, I added a readout for it.

Does them going down clear the ranges?

Not unless it remains offline for more than two weeks.

Plugging my hitrates into the formula, I should have gotten ~3594.24 kgp. Maybe the dashboard #s are on some kind of sliding average and traffic to my clients has gone down more than what the dashboard would suggest, I don't know.

As other people have pointed out, GP is calculated from raw hits, the readout on the H@H page is an average. So if your traffic changed significantly, it'll take a while to reflect the current hitrate. (In other words, it's not "still going down", it's just settling to the new rate.)

I've increased my max speed about 15%, and actual outbound traffic increased at least 5% (most of time it can reach the max speed, except for a few hours in the early morning), but my hitrate still dropped 10%~20% (I didn't remember the accurate hitrate before). Would it caused by the update recently?

I've increased my max speed about 15%, and actual outbound traffic increased at least 5% (most of time it can reach the max speed, except for a few hours in the early morning), but my hitrate still dropped 10%~20% (I didn't remember the accurate hitrate before). Would it caused by the update recently?

As other people have pointed out, GP is calculated from raw hits, the readout on the H@H page is an average. So if your traffic changed significantly, it'll take a while to reflect the current hitrate. (In other words, it's not "still going down", it's just settling to the new rate.)

So it looks like my hitrate is about 10% of what it once was. This is expected to be temporary though?

Other people have said that restarting their h@h process helped, is that true? Should I do that?

So it looks like my hitrate is about 10% of what it once was. This is expected to be temporary though?

Other people have said that restarting their h@h process helped, is that true? Should I do that?

You have already been told your hit rate will take time to adjust - it is as simple as not doing anything. (IMG:[invalid] style_emoticons/default/smile.gif)

Other people have said that restarting their h@h process helped, is that true? Should I do that?

Does the opposite if you are doing it for this purpose, so no, you shouldn't.