I´m using the Google Chrome debugging tools. There you can see the
getTranslationLanguages request which is WAITING for 12 seconds. But, anyway, I
don´t know the reason why.
Please let my attach the screenshot.
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: RE: Issue with Unicorn: Big latency when getting a request
Date: Fri, 14 Nov 2014 11:12:16 +0100
I have no idea about what can it be. I don´t see any blog, issue or post on
internet related to this. It´s strange this is only happening to me.
Anyway, remember the issue is not happening when I replace Unicorn with webRick.
> Date: Fri, 14 Nov 2014 10:02:08 +0000
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: Issue with Unicorn: Big latency when getting a request
>
> Roberto Cordoba del Moral <[email protected]> wrote:
> > Hi Eric,
> >
> > as you don´t like web. I don´t know if you read my latest updates.
> > Please, find them attached. I don´t know if they could be helpful
> > tracks. UPDATE: I don´t know why it seems to be related to cache or
> > cookies. When I delete browsing history with cache and cookies in my
> > browser and I load the site the issue doesn´t happen anymore. After
> > that, if I just refresh the page, the issue happens. Thanks,Roberto.
>
> It's probably something related to your frontend/Angular setup (which I
> know nothing about). Try disabling cookies + cache in your browser
> completely... Some browsers have extensions/plugins which can trace
> HTTP requests, too.
>
> > I´m not pretty sure how to crank up the verbosity of nginx although
> > I think I got it, because when I restart Nginx I get next logs:
>
> Server debugging:
>
> Uncomment one of your "error_log" lines in your nginx conf:
>
> error_log logs/error.log debug;
>
> (you can change the path, of course)
>
> I suggest using your Ubuntu (or any GNU/Linux) test environment which
> has strace. I cannot support any software on Darwin.
>
> You may also use tcpdump/strace on your browser, too, but I suspect for
> your case it'll be easier to use whatever debugging tools +
> plugins/extensions your browser supports.
>
> This really doesn't seem to be a unicorn or nginx bug, though...
I'm using the Google Chrome debugging tools. There you can see the
getTranslationLanguages request which is WAITING for 12 seconds. But,
anyway, I don't know the reason why.
Please let my attach the screenshot.
__________________________________________________________________
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: RE: Issue with Unicorn: Big latency when getting a request
Date: Fri, 14 Nov 2014 11:12:16 +0100
I have no idea about what can it be. I don't see any blog, issue or
post on internet related to this. It's strange this is only happening
to me.
Anyway, remember the issue is not happening when I replace Unicorn with
webRick.
> Date: Fri, 14 Nov 2014 10:02:08 +0000
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: Issue with Unicorn: Big latency when getting a request
>
> Roberto Cordoba del Moral <[email protected]> wrote:
> > Hi Eric,
> >
> > as you don't like web. I don't know if you read my latest updates.
> > Please, find them attached. I don't know if they could be helpful
> > tracks. UPDATE: I don't know why it seems to be related to cache or
> > cookies. When I delete browsing history with cache and cookies in
my
> > browser and I load the site the issue doesn't happen anymore. After
> > that, if I just refresh the page, the issue happens.
Thanks,Roberto.
>
> It's probably something related to your frontend/Angular setup (which
I
> know nothing about). Try disabling cookies + cache in your browser
> completely... Some browsers have extensions/plugins which can trace
> HTTP requests, too.
>
> > I'm not pretty sure how to crank up the verbosity of nginx although
> > I think I got it, because when I restart Nginx I get next logs:
>
> Server debugging:
>
> Uncomment one of your "error_log" lines in your nginx conf:
>
> error_log logs/error.log debug;
>
> (you can change the path, of course)
>
> I suggest using your Ubuntu (or any GNU/Linux) test environment which
> has strace. I cannot support any software on Darwin.
>
> You may also use tcpdump/strace on your browser, too, but I suspect
for
> your case it'll be easier to use whatever debugging tools +
> plugins/extensions your browser supports.
>
> This really doesn't seem to be a unicorn or nginx bug, though...
