-
Notifications
You must be signed in to change notification settings - Fork 19
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
Is the redirect slow for anyone else? #42
Comments
Would you be able to post an example server configuration that you’re calling? |
Sure, one example that has a front-end is datasette. chromehistorydb.json {
"cwd": "<my code folder, unrelated to datasette>",
"cmd": "datasette ~/Library/Application\\ Support/Google/Chrome/Default/History --nolock -p 7826",
"env": {
"PATH": "<lots of PATH>",
"PORT": 7826
}
} Can actually see the 5 second delay in the logs: 18:35:07 - Resolve chromehistorydb |
Out of curiosity, how many server configurations do you have? |
less than 20 |
It seems possible that the issue might be specifically with the service you are running: simonw/datasette#316 (comment) I tried executing the same thing on a brand new Chrome History file and it loaded up instantaneously. Let me know if you can somehow create a backup of your history file and test with a new one from scratch to see what the timings are. |
I just tried with another service that has a fixed port + frontend With the chromehistory service - it takes 5 seconds each time. |
I use chalet as a server catalog. I have fixed ports set up for most services. I hit localhost:2000/server-name to get redirected to the port.
It takes 3-4 seconds to redirect sometimes, I'm wondering why it should take any time at all, what happens other than the redirect? Is there anything to configure to make it redirect without checks?
Thanks
The text was updated successfully, but these errors were encountered: