Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS cache #660

Open
d47081 opened this issue Apr 3, 2024 · 2 comments
Open

DNS cache #660

d47081 opened this issue Apr 3, 2024 · 2 comments
Labels
enhancement New feature or request suggestion Suggestion for future consideration

Comments

@d47081
Copy link

d47081 commented Apr 3, 2024

What about cache DNS results for some time instead of resolve host on every page request?

It would increase pages loading speed because currently gemtext open slower than huge HTML in FF

I mean something like about:config option:

network.dnsCacheExpiration
@skyjake skyjake added the enhancement New feature or request label Apr 5, 2024
@skyjake
Copy link
Owner

skyjake commented Apr 5, 2024

While caching DNS results in-app could provide benefits in some cases, you are the first to report DNS being noticeably slow. May I ask if there is something in your local network setup that makes DNS particularly slow? Have you considered running a local DNS server that caches the results for you?

In general, I would rather not implement this kind of low-level networking features in Lagrange, as DNS caching is typically handled adequately by the operating system and the router(s).

@skyjake skyjake added the suggestion Suggestion for future consideration label Apr 5, 2024
@d47081
Copy link
Author

d47081 commented Apr 5, 2024

I've really found this latency on the machine connecting remote DNS over Yggdrasil (that has 1m cache for handshake on first connection). Also DNS provider had slow ping there, so resolve takes about 500ms of delays on each page request.

What's interesting, I have no discomfort in FireFox and found this problem by navigation in Gemini space only, where is strange to see loading tray for those few bytes of gemtext.

Agreed, that could be solved by system-mide cache, but it's not always useful (when some services sensitive to this cache applied commonly).

Suppose that's just useful feature request to make response immediate, call it fast page loading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request suggestion Suggestion for future consideration
Projects
None yet
Development

No branches or pull requests

2 participants