From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Thread.current
Date: Fri, 7 Jan 2011 18:57:20 -0800 [thread overview]
Message-ID: <20110108025720.GA16042@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTi=OKoLcLDCXacgXOa+nCST0oNt6_i4JKLbKMK7B@mail.gmail.com>
Jimmy Soho <jimmy.soho@gmail.com> wrote:
> Hi All,
>
> Having an akward noob moment... I have unicorn_rails (1.1.5) running
> with 2 workers, with rails 2.3.10 in development mode. In
> environment.rb at the bottom I have this line of code:
>
> puts "#{Time.current} #{Thread.current.object_id}: #{Thread.current.keys.inspect}"
Add the PID ($$), too:
puts "#{Time.current} #$$ #{Thread.current.object_id}: #{Thread.current.keys.inspect}"
> In a simple controller I have this:
>
> def index
> puts "#{Time.current} #{Thread.current.object_id}: #{Thread.current.keys.inspect}"
> sleep 5
> puts "#{Time.current} #{Thread.current.object_id}: #{Thread.current.keys.inspect}"
> render :text => "foo"
> end
>
> In window 1 I tail log/unicorn.log.
> In windows 2 and 3 I start at about the same time: curl http://localhost:3000
>
> The output is this:
>
> 2011-01-08 01:53:56 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
> worker=1 ready
> 2011-01-08 01:53:56 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
> worker=0 ready
> 2011-01-08 01:53:57 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
> 2011-01-08 01:53:59 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
> 2011-01-08 01:54:02 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
> 2011-01-08 01:54:04 UTC 2148444460: [:__inspect_key__, :i18n_config,
> :__recursive_key__]
>
> Looking at the timings the 2 requests seem to have been handled in
> parallel, as expected.
Yes, that's because you have two worker *processes*
> However, the Thread.current value within those parallel requests is
> always the same.
Just a lucky coincidence :)
> Are two separate requests not handled by different threads? How does
> that work??
Threads (and any other object) object_ids are unique to each process.
They are not unique within all the processes of a machine.
When dealing with native threads under Linux, gettid() is a non-portable
Linux syscall to get the unique identifier of a thread throughout the
entire system. That's the only way I know of if you want a single
unique identifier (and of course prepending the PID to it).
--
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-01-08 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 2:00 Thread.current Jimmy Soho
2011-01-08 2:57 ` Eric Wong [this message]
2011-01-08 3:09 ` Thread.current Curtis j Schofield
2011-01-08 5:54 ` Thread.current Jimmy Soho
2011-01-11 22:52 ` Thread.current Jimmy Soho
2011-01-11 23:12 ` Thread.current Eric Wong
2011-01-11 23:12 ` Thread.current Jordan Ritter
2011-01-12 3:07 ` Thread.current Jimmy Soho
2011-01-13 4:26 ` Thread.current Eric Wong
2011-01-13 16:46 ` Thread.current Jordan Ritter
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=20110108025720.GA16042@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.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).