Closed Heclalava closed 8 months ago
请附上得出你这结论的图片,证明下
What protocol are you using What's the version of xray core on your server
@KoinuDayo 1.8.4
1.8.3
Although 1.8.4 seems to be performing a little better now, but still a stark difference in speed between 1.8.4 and 1.8.3.
@Fangliding I am using xray REALITY. Both my router and VPS will either run 1.8.3 or 1.8.4 simultaneously when testing. Same core version on both VPS and router during each test.
@KoinuDayo 1.8.4
1.8.3
Although 1.8.4 seems to be performing a little better now, but still a stark difference in speed between 1.8.4 and 1.8.3.
@Fangliding I am using xray REALITY. Both my router and VPS will either run 1.8.3 or 1.8.4 simultaneously when testing. Same core version on both VPS and router during each test.
Did you use vision? and did you try to use 1.8.3 server 1.8.4 client or 1.8.4 server 1.8.3 client more comparisons help locate problem
@Fangliding
Yes I am using xtls-rprx-vision.
1.8.4 on VPS and 1.8.3 on router
1.8.3 on VPS and 1.8.4 on router
So it seems when the cores are not matched on the router and the VPS the speeds are similar. So the issue only appears when both the router and the VPS are on 1.8.4.
I am using the FancySS HND v8 plugin for Merlin Koolshare on Asus RT-AC86U. I downloaded the Xray-linux-arm64-v8a.zip from the 1.8.4 release, and compressed it with command upx-ucl --lzma --ultra-brute xray
I then upload that to my router by SCP to 192.168.0.1:/jffs/.koolshare/bin
@Fangliding
Yes I am using xtls-rprx-vision.
1.8.4 on VPS and 1.8.3 on router
1.8.3 on VPS and 1.8.4 on router
So it seems when the cores are not matched on the router and the VPS the speeds are similar. So the issue only appears when both the router and the VPS are on 1.8.4.
I am using the FancySS HND v8 plugin for Merlin Koolshare on Asus RT-AC86U. I downloaded the Xray-linux-arm64-v8a.zip from the 1.8.4 release, and compressed it with command
upx-ucl --lzma --ultra-brute xray
I then upload that to my router by SCP to 192.168.0.1:/jffs/.koolshare/bin
It seem sone features added in 1.8.4 cause the problem. If one of server or client is 1.8.3, It will not function make the speed normal Try to download xray core here https://github.com/XTLS/Xray-core/actions/runs/6009175068
you can find different xray core here https://github.com/XTLS/Xray-core/actions/workflows/release.yml If the speed is normal, try a later build. If the speed is reduced, try an earlier build to locate the commit that caused the problem
@Fangliding ok so that will take a while to test, just because of the length of time required to compress the core with upx. I will report back later if I manage to find the commit causing the problem.
@Heclalava Is upx compress necessary? I think you can direct run client on pc, it can save much time
@Heclalava Is upx compress necessary? I think you can direct run client on pc, it can save much time
As I mostly use the router for xray, and this is where the issue is detected, I think continuing testing via the router is necessary. Also I believe v2rayA doesn't yet support xray reality vision yet. So because of the limited space on the jffs partition on the router, I do need to shrink it down with upx.
@Fangliding the Xray-linux-arm64-v8a core from https://github.com/XTLS/Xray-core/actions/runs/6009175068 has the same issue. So I will have to try the older versions from https://github.com/XTLS/Xray-core/actions/workflows/release.yml
@Fangliding this commit seems fine https://github.com/XTLS/Xray-core/actions/runs/5965516913. So it is one of the commits newer than this, that the problem seems have been introduced. I will continue testing to see if I can isolate the specific commit that causes the problem.
Ok so this commit has the probelm https://github.com/XTLS/Xray-core/actions/runs/5983620450
So the problem was introduced from one of these commits:
Will speed be affected if reality is not used?
@Fangliding last good commit is https://github.com/XTLS/Xray-core/actions/runs/5966097424
Problems start from commit https://github.com/XTLS/Xray-core/actions/runs/5969608681
Will speed be affected if reality is not used?
I think for now I will leave it in this commit that seems to be working and see how it goes for the next couple days, if any issues I will revert back to 1.8.3
@Fangliding last good commit is https://github.com/XTLS/Xray-core/actions/runs/5966097424
Problems start from commit https://github.com/XTLS/Xray-core/actions/runs/5969608681
I forgot one thing only use the main branch build(https://github.com/XTLS/Xray-core/actions/workflows/release.yml?query=branch%3A%22main%22 ignore xxxxxx:main, it shoud not display), other banch might form other repo And thank for your patience testing this
@Fangliding last good commit is https://github.com/XTLS/Xray-core/actions/runs/5966097424 Problems start from commit https://github.com/XTLS/Xray-core/actions/runs/5969608681
I forgot one thing only use the main branch build(https://github.com/XTLS/Xray-core/actions/workflows/release.yml?query=branch%3A%22main%22 ignore xxxxxx:main, it shoud not display), other banch might form other repo And thank for your patience testing this
Ahh shit, I see there are a lot of commits between 1.8.3 and 1.8.4 to test. Hopefully I can narrow in when I know where I am getting problems and where I am not.
well im also interested in the result so please keep on testing i had the same problem but during switch from 1.8.1 to 1.8.4 i also switched from BBR to cubic since the RTT is 200 or above to my server so i took it as the change from bbr to cubic and reverted back to using BBR again if you found out that the cause is 1.8.4 i simply can revert server xray core to 1.8.3 and clients wont have a problem thanks alot for your patience and testings have a wonderful day
@Fangliding testing I have hit an obstacle. A lot of the commits have expired, so unable to localize from which commit the problem starts:
It could be any of them from the 1.8.3 release up to the 1.8.4 release, but with most expired, it make testing very difficult.
I encountered the same problem. When I used 1.8.4 on the server, the speed was very slow. The web page sometimes took more than ten seconds to open. But when I restored it to 1.8.3, everything was normal. I am using xtls-rprx-vision.
I can confirm that this is fixed on version 1.8.7.
我可以确认这个问题在1.8.7版本已经修复了。
@1337anonboi great
ok
I have noticed a dramatic drop in download speed since switching to 1.8.4. Before on 1.8.3 I would get 90 Mbps download through my VPS, now on 1.8.4 I never get more than 30 Mbps.
I have been testing the last few days, by switching back and forwards between the 2 versions of the core on both my router and VPS, and it is definitely much faster on 1.8.3.