Skip to content

Commit 20922c8

Browse files
authored
Add JS Interactive 2018 banner (#1732)
* Fix logo link * Fix image link in blog post * Add JS Interactive 2018 banner * Fix http -> https
1 parent ea0f042 commit 20922c8

5 files changed

Lines changed: 14 additions & 5 deletions

File tree

layouts/css/_base.styl

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,11 @@ a:hover
3434
background-color transparent
3535
color #fff
3636

37-
a.imagelink:hover
38-
background-color transparent
37+
a.imagelink
38+
display inline-block
39+
40+
&:hover
41+
background-color transparent
3942

4043
strong,
4144
b

layouts/index.hbs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@
1212

1313
{{{ contents }}}
1414

15+
<p>
16+
<a class="imagelink" href="https://events.linuxfoundation.org/events/js-interactive-2018/?utm_source=nodesite&utm_medium=homepagebanner&utm_campaign=jsint18&utm_term=eventpage">
17+
<img src="/static/images/jsinteractive-2018-banner.png" alt="JS Interactive on October 10-12, 2018 in Vancouver, Canada">
18+
</a>
19+
</p>
20+
1521
{{#if project.banner.visible}}
1622
<p class="home-version home-version-banner">
1723
<a href="{{ project.banner.link }}">{{#if project.banner.text}}{{{ project.banner.text }}}{{else}}{{{ labels.banner }}}{{/if}}</a>

layouts/partials/header.hbs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<header>
22
<div class="container">
33

4-
<a href="/{{site.locale}}" id="logo">
4+
<a href="/{{site.locale}}/" id="logo">
55
<img src="/static/images/logo.svg" alt="node.js">
66
</a>
77

locale/en/blog/uncategorized/profiling-node-js.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ slug: profiling-node-js
88
layout: blog-post.hbs
99
---
1010

11-
It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="http://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="http://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):
11+
It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="https://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="https://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):
1212

1313
<ol>
1414
<li>Run your Node.js program as usual.</li>
@@ -27,7 +27,7 @@ It's incredibly easy to visualize where your Node program spends its time using
2727

2828
You'll be looking at something like this:
2929

30-
<a href="https://www.cs.brown.edu/~dap/helloworld.svg" class="imagelink"><img src="https://www.cs.brown.edu/~dap/helloworld.svg" alt="'Hello World' HTTP server flame graph" /></a>
30+
<a href="https://cs.brown.edu/people/dapachec/helloworld.svg" class="imagelink"><img src="https://cs.brown.edu/people/dapachec/helloworld.svg" alt="'Hello World' HTTP server flame graph" /></a>
3131

3232
This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the <a href="https://nodejs.org">Node.js</a> home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.
3333

14.3 KB
Loading

0 commit comments

Comments
 (0)