So I ended up with the same results using Node 0.8.x. Also tried out
nhttpsnoop and ended up with this:
[root@00-0c-29-ab-31-af /development/nhttpsnoop]# ./nhttpsnoop -l -c -o
time,pid,probe,which,latency,method,raddr,rport,url
TIMEPID PROBELATENCY METHOD RADDRRPORT
I'll give both nhttpsnoop and older versions of node a try shortly, haven't
had a chance to get back at it since last night. I'll reply if anything
interesting turns up.
Thanks!
On Mon, Feb 5, 2018 at 2:42 PM, David Pacheco wrote:
> On Sun, Feb 4, 2018 at 8:02 AM, Brad Gardner wrote:
>
>> Hell
On Sun, Feb 4, 2018 at 8:02 AM, Brad Gardner wrote:
> Hello!
>
> I'm working on learning to use DTrace to profile NodeJS applications and
> have hit a wall that I'm hoping to get some additional insight on.
>
> I have a NodeJS application that is sending an HTTP request to
> https://example.com e
Hello!
I'm working on learning to use DTrace to profile NodeJS applications and
have hit a wall that I'm hoping to get some additional insight on.
I have a NodeJS application that is sending an HTTP request to
https://example.com every 5 seconds. This is working and getting a proper
response.
*I
