unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Roberto Cordoba del Moral <roberto.chingon@hotmail.com>
Cc: unicorn-public@bogomips.org
Subject: Re: Issue with Unicorn: Big latency when getting a request
Date: Fri, 14 Nov 2014 10:02:08 +0000	[thread overview]
Message-ID: <20141114100208.GA7416@dcvr.yhbt.net> (raw)
In-Reply-To: <DUB126-W466F54DFDA0FC42E8AB27BF88C0@phx.gbl>

Roberto Cordoba del Moral <roberto.chingon@hotmail.com> 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...

  reply	other threads:[~2014-11-14 10:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 19:46 Issue with Unicorn: Big latency when getting a request Roberto Cordoba del Moral
2014-11-13  7:12 ` Roberto Cordoba del Moral
2014-11-13 21:03   ` Eric Wong
2014-11-14  6:46     ` Roberto Cordoba del Moral
2014-11-14  7:19       ` Eric Wong
2014-11-14  9:09         ` Roberto Cordoba del Moral
2014-11-14  9:32           ` Roberto Cordoba del Moral
2014-11-14 10:02             ` Eric Wong [this message]
2014-11-14 10:12               ` Roberto Cordoba del Moral
2014-11-14 10:15                 ` Roberto Cordoba del Moral
2014-11-14 10:28                   ` Eric Wong
2014-11-14 10:51                     ` Roberto Cordoba del Moral
2014-11-14 11:03                       ` Eric Wong
2014-11-14 11:15                         ` Roberto Cordoba del Moral
2014-11-14 15:01                         ` Roberto Cordoba del Moral
2014-11-14 18:34                           ` Eric Wong
2014-11-14 22:36                             ` Roberto Cordoba del Moral

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141114100208.GA7416@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=roberto.chingon@hotmail.com \
    --cc=unicorn-public@bogomips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).