Thread overview |
---|
February 03, 2017 The reason of vibed slow down (request timeout) | ||||
---|---|---|---|---|
| ||||
I have simple web-app. Server part is based on vibed http://194.87.235.42:8080/ I can't understand the reason of issue. after some days of work when I trying to open it in web-browser it's begin opening very slooowly, or like now does not opens at all. On mobile web-browser I am getting request-timeout. How I can diagnostic the reason of such behavior? The sources code is here https://github.com/bubnenkoff/Geoportal2 |
February 03, 2017 Re: The reason of vibed slow down (request timeout) | ||||
---|---|---|---|---|
| ||||
Posted in reply to Suliman | If I open it's from VPS (as localhost:8080) it's work same as from Internet (no do not open at all). |
February 03, 2017 Re: The reason of vibed slow down (request timeout) | ||||
---|---|---|---|---|
| ||||
Posted in reply to Suliman | On Friday, 3 February 2017 at 06:46:37 UTC, Suliman wrote:
> If I open it's from VPS (as localhost:8080) it's work same as from Internet (no do not open at all).
If problem is reproducible on localhost - very good, just debug it. If you have memory leak and can't figure out source, try valgrind tool - it can help.
P.S. Русские комментарии в коде - плохой стиль.
|
February 03, 2017 Re: The reason of vibed slow down (request timeout) | ||||
---|---|---|---|---|
| ||||
Posted in reply to Suliman | On Friday, 3 February 2017 at 06:46:37 UTC, Suliman wrote:
> If I open it's from VPS (as localhost:8080) it's work same as from Internet (no do not open at all).
One this I may suggest is the port if its used already (8080). Try to use;
import std.process: environment;
settings.port = environment.get("PORT", "8080").to!short;
|
February 04, 2017 Re: The reason of vibed slow down (request timeout) | ||||
---|---|---|---|---|
| ||||
Posted in reply to crimaniak | On Friday, 3 February 2017 at 07:44:15 UTC, crimaniak wrote: > On Friday, 3 February 2017 at 06:46:37 UTC, Suliman wrote: >> If I open it's from VPS (as localhost:8080) it's work same as from Internet (no do not open at all). > > If problem is reproducible on localhost - very good, just debug it. If you have memory leak and can't figure out source, try valgrind tool - it can help. > > > P.S. Русские комментарии в коде - плохой стиль. This tool is nix only. I checked memory footprint, and it's show that app use impossible low memory http://3.1m.yt/cCdzA.png I reread sources and still don't understand where it can be problem place. |
Copyright © 1999-2021 by the D Language Foundation