Bad connection from Europe #2
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/gitea.com#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should think about improving connection/performance for users in Europe and other regions.
Please consider these tests:
Europe: https://www.webpagetest.org/result/190709_W5_8abc8dfa85d813efe38382cfe8196583/
Asia: https://www.webpagetest.org/result/190709_8R_ab60f8fddad4ddea0809f6f7d8592eb8/
Connections from Asisa seem to be at least 50% faster then the connection from Europe / Frankfurt, Germany.
This supports my impressions from using Gitea.com on daily basis.
What if we put gitea.com behind cloudflare, and set
SSH_DOMAIN
to a domain that directly connects to the servers. This will break existinggit clone git@gitea.com:...
though. This will have the added bonus of adding IPv6 to the web interface.Cloudflare only accelerate static page I think.
I think we should create a subdomain static.gitea.com to serve all static content, include js/css/images/html . I have created PR https://github.com/go-gitea/gitea/pull/6341 but will have time finished.
The static.gitea.com could be served by cloudflare with free plan.
sidenote PR is now on https://github.com/go-gitea/gitea/pull/7911
Same results from Argentina 😢
https://www.webpagetest.org/result/191008_M0_3c9f3c764b8ee58d29d79b443c129710/
I think we can at first solve static resources and CDN problem via https://github.com/go-gitea/gitea/pull/7911 .
We have enabled CDN for static resources. Is this still a problem? @jonasfranz
It improved slightly, but only one second. Still takes 5s to load fully.
https://www.webpagetest.org/result/191231_RC_dda250367cae4d12883f9cb7fc764d73/
@kolaente I also tested github, https://www.webpagetest.org/result/200101_HV_ff9f862e194bc42a89d70c62a261be22/
It seems github also spent 5s to load fully.
But for
Start Render
, gitea is 3.900s, github is 1.400s .Slowness is primarly due to latency. I see around 350ms to gitea.com vs 100ms to try.gitea.io which feels much faster because of it.
gitea.com runs on tls 1.2. I imagine tls 1.3 with 0-rtt tls handshake would certainly help.
I think this situation should have now improved somewhat with the new host.
@zeripath Glad to know that.