last data update: 2011/10/20, 10:58

Website loading time

during the test: 0.32 s

cable connection (average): 0.56 s

DSL connection (average): 0.8 s

modem (average): 13.47 s

HTTP headers

Information about DNS servers

paperplanes.deA173.45.232.115IN900
paperplanes.deSOAa.ns.joker.comhostmaster.joker.com201104186010240 7200 1209600 86400 IN 43200
paperplanes.deMX20ALT2.ASPMX.L.GOOGLE.comIN43200
paperplanes.deMX30ASPMX2.GOOGLEMAIL.comIN43200
paperplanes.deMX30ASPMX3.GOOGLEMAIL.comIN43200
paperplanes.deMX30ASPMX4.GOOGLEMAIL.comIN43200
paperplanes.deMX30ASPMX5.GOOGLEMAIL.comIN43200
paperplanes.deMX10ASPMX.L.GOOGLE.comIN43200
paperplanes.deMX20ALT1.ASPMX.L.GOOGLE.comIN43200
paperplanes.deNSb.ns.joker.comIN43200
paperplanes.deNSc.ns.joker.comIN43200
paperplanes.deNSa.ns.joker.comIN43200

Received from the first DNS server

Request to the server "paperplanes.de"
You used the following DNS server:
DNS Name: b.ns.joker.com
DNS Server Address: 66.252.5.4#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 31222
flag: qr aa rd REQUEST: 1, ANSWER: 12, AUTHORITY: 0, ADDITIONAL: 3

REQUEST SECTION:
paperplanes.de. IN ANY

ANSWER SECTION:
paperplanes.de. 86400 IN NS a.ns.joker.com.
paperplanes.de. 86400 IN NS b.ns.joker.com.
paperplanes.de. 86400 IN NS c.ns.joker.com.
paperplanes.de. 86400 IN MX 30 ASPMX4.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 20 ALT2.ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 30 ASPMX3.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 30 ASPMX5.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 20 ALT1.ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 10 ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 30 ASPMX2.GOOGLEMAIL.com.
paperplanes.de. 86400 IN SOA a.ns.joker.com. hostmaster.joker.com. 2011041860 10240 7200 1209600 86400
paperplanes.de. 900 IN A 173.45.232.115

SECTION NOTES:
a.ns.joker.com. 7200 IN A 207.44.185.100
b.ns.joker.com. 7200 IN A 66.252.5.4
c.ns.joker.com. 7200 IN A 207.44.185.10

Received 379 bytes from address 66.252.5.4#53 in 30 ms

Received from the second DNS server

Request to the server "paperplanes.de"
You used the following DNS server:
DNS Name: c.ns.joker.com
DNS Server Address: 207.44.185.10#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 26683
flag: qr aa rd REQUEST: 1, ANSWER: 12, AUTHORITY: 0, ADDITIONAL: 3

REQUEST SECTION:
paperplanes.de. IN ANY

ANSWER SECTION:
paperplanes.de. 86400 IN NS a.ns.joker.com.
paperplanes.de. 86400 IN NS b.ns.joker.com.
paperplanes.de. 86400 IN NS c.ns.joker.com.
paperplanes.de. 86400 IN MX 30 ASPMX4.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 20 ALT2.ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 30 ASPMX3.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 30 ASPMX5.GOOGLEMAIL.com.
paperplanes.de. 86400 IN MX 20 ALT1.ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 10 ASPMX.L.GOOGLE.com.
paperplanes.de. 86400 IN MX 30 ASPMX2.GOOGLEMAIL.com.
paperplanes.de. 86400 IN SOA a.ns.joker.com. hostmaster.joker.com. 2011041860 10240 7200 1209600 86400
paperplanes.de. 900 IN A 173.45.232.115

SECTION NOTES:
a.ns.joker.com. 7200 IN A 207.44.185.100
b.ns.joker.com. 7200 IN A 66.252.5.4
c.ns.joker.com. 7200 IN A 207.44.185.10

Received 379 bytes from address 207.44.185.10#53 in 46 ms

Subdomains (the first 50)

Typos (misspells)

oaperplanes.de
laperplanes.de
-aperplanes.de
0aperplanes.de
pzperplanes.de
psperplanes.de
pwperplanes.de
pqperplanes.de
paoerplanes.de
palerplanes.de
pa-erplanes.de
pa0erplanes.de
papwrplanes.de
papsrplanes.de
papdrplanes.de
paprrplanes.de
pap4rplanes.de
pap3rplanes.de
papeeplanes.de
papedplanes.de
papefplanes.de
papetplanes.de
pape5planes.de
pape4planes.de
paperolanes.de
paperllanes.de
paper-lanes.de
paper0lanes.de
paperpkanes.de
paperppanes.de
paperpoanes.de
paperplznes.de
paperplsnes.de
paperplwnes.de
paperplqnes.de
paperplabes.de
paperplames.de
paperplajes.de
paperplahes.de
paperplanws.de
paperplanss.de
paperplands.de
paperplanrs.de
paperplan4s.de
paperplan3s.de
paperplanea.de
paperplanez.de
paperplanex.de
paperplaned.de
paperplanee.de
paperplanew.de
aperplanes.de
pperplanes.de
paerplanes.de
paprplanes.de
papeplanes.de
paperlanes.de
paperpanes.de
paperplnes.de
paperplaes.de
paperplans.de
paperplane.de
apperplanes.de
ppaerplanes.de
paeprplanes.de
papreplanes.de
papeprlanes.de
paperlpanes.de
paperpalnes.de
paperplnaes.de
paperplaens.de
paperplanse.de
ppaperplanes.de
paaperplanes.de
papperplanes.de
papeerplanes.de
paperrplanes.de
paperpplanes.de
paperpllanes.de
paperplaanes.de
paperplannes.de
paperplanees.de
paperplaness.de

Location

IP: 173.45.232.115

continent: NA, country: United States (USA), city: Saint Louis

Website value

rank in the traffic statistics:

There is not enough data to estimate website value.

Basic information

website build using CSS

code weight: 92.08 KB

text per all code ratio: 80 %

title: paperplanes. software development that flies.

description: The weblog of Mathias Meyer, freelance software developer.

keywords: freelancer, software development, web development, development, rails, ruby on rails, blog, berlin, germany, coaching, code reviews

encoding: utf-8

language: en

Website code analysis

one word phrases repeated minimum three times

PhraseQuantity
the441
to425
of281
and244
you213
is172
in169
your157
that133
on131
for122
be121
it115
or105
with79
an79
all69
not69
it's63
data61
but60
when60
can59
are57
have57
The54
will54
just51
as50
from50
more46
at44
application42
like41
any38
up36
some36
what35
one34
database34
should33
which33
using33
into33
by32
tools32
if32
When31
do31
much31
get29
this29
them29
file29
know29
out28
has28
You28
need27
It27
This26
don't26
something25
time25
over25
even25
about25
use25
new24
log24
code23
If22
also22
important22
so22
metrics22
they22
available22
most21
how21
than21
process20
they're20
you're20
I'm20
good19
no19
server19
doesn't19
set19
because18
infrastructure18
that's18
system18
In17
only17
my17
last17
other16
you'll16
It's16
usually16
where15
book15
call15
read15
way15
never15
been15
able15
monitoring15
very15
lot15
specific14
running14
their14
write14
descriptors14
first14
EventMachine14
there's14
pretty14
add13
There's13
may13
operations13
me13
every13
these13
level13
it.13
event13
servers13
simply13
go12
being12
happens12
through12
users12
connection12
right12
MongoDB12
find12
services12
does12
things12
make12
list11
too11
open11
needs11
bit11
start11
keep11
then11
e.g.11
memory11
always11
was11
you.11
look11
number11
thing10
used10
run10
comes10
time.10
service10
makes10
single10
want10
different10
two10
application,10
kill10
external10
asynchronous10
web10
having10
there10
analyze10
case10
return10
epoll10
working10
going9
user9
either9
what's9
it,9
can't9
But9
access9
everything9
directly9
work9
both9
whatever9
easier9
written9
reading9
What9
nothing9
files9
still9
operating9
sure9
next9
problem9
You'll8
Unix8
sort8
people8
request8
Rails8
For8
time,8
matter8
problem.8
means8
own8
around8
really8
infrastructure,8
big8
without8
infrastructure.8
I/O8
bunch8
processes8
turn8
why8
must8
take8
collect8
worth8
On7
code,7
check7
wait7
system,7
site7
They7
its7
couple7
existing7
setting7
deal7
business7
on.7
could7
callbacks7
Everything7
similar7
track7
kind7
reason7
doing7
after7
New7
place7
Most7
application.7
down7
before7
see7
resources7
MongoDB,7
shouldn't7
them.7
Don't7
server,7
guy7
Your7
tool6
coming6
Use6
care6
another6
production6
end6
you,6
tell6
build6
servers,6
between6
consider6
seem6
alerting6
Whenever6
thresholds6
monitoring,6
features6
databases6
idea6
source6
based6
Level6
all,6
calls6
activity6
world6
immediately6
writes6
allowing6
takes6
back6
processing6
though6
currently6
come6
As6
me,6
data.6
descriptor6
EventMachine,6
disk6
stuff6
disk,6
general6
swap6
available.6
actually6
give6
All6
ready6
our6
library6
someone6
best5
process,5
queries5
logging5
they'll5
inside5
anything5
standard5
flush5
durability5
didn't5
whole5
provider5
method5
accept5
MongoDB's5
his5
network5
These5
notice5
long5
problems5
rely5
loop,5
libraries5
piece5
though,5
amount5
think5
push5
cycle5
part5
chance5
Tags:5
Note5
here,5
related5
evented5
false5
Ruby5
brings5
while5
memory,5
And5
less5
Application5
tasks5
place,5
buffer5
TCP5
requires5
HTTP5
done5
same5
basic5
larger5
magic5
point5
kinds5
feature5
C++5
learn5
won't5
failure.5
page5
basically5
loop5
20115
socket5
I'll5
(line5
Posted5
Mathias5
now,5
How5
many5
select()5
everyone5
Meyer5
create5
updates5
Yes,5
includes5
So5
reach5
not.5
deeper5
Do5
that.5
play5
throw5
experience5
sense5
value4
place.4
well4
generating4
least4
skill4
background4
Fibers4
checking4
Instead4
longer4
is,4
too,4
become4
block4
systems4
fired4
simple4
pile4
show4
descriptors.4
reads4
Data4
called4
Infrastructure4
certain4
once4
Think4
At4
enough4
They're4
left4
incredibly4
already4
around.4
built4
setup4
impossible4
associated4
here4
properly4
fully4
do,4
EventMachine's4
allow4
system.4
connections4
memory.4
That's4
additional4
syslog4
internal4
To4
soon4
slow4
Node.js4
terrible4
caused4
probably4
Every4
area4
speed4
automate4
abundance4
databases,4
better4
aren't4
until4
programming4
configuration4
descriptors,4
case,4
final4
solve4
line4
virtual4
we4
Just4
easy4
happen4
way,4
eventually4
knowing4
tests4
valuable4
again,4
Which4
indirectly4
maybe4
acceptable4
stop4
errors4
trying4
latency4
talk4
runs4
disk.4
While4
Munin4
data,4
durable4
writing4
current4
gathering4
-94
per4
had4
ensure4
handle4
query4
lost4
component4
mean4
hours4
now.4
Web4
let4
quickly4
useful4
easily4
availability4
end.4
instances3
allowed3
spike3
memory-mapped3
wrong3
details,3
pages.3
problem,3
taking3
value.3
lose3
particular3
read,3
603
database.3
After3
calling3
full3
custom3
deployment3
pages3
receive_data3
What's3
small3
given3
pointing3
constantly3
requests3
(think3
trends3
There3
Let3
NoSQL3
biggest3
increases3
waiting3
exactly3
object3
software3
thread3
made3
aware3
snippet3
involves3
far3
replica3
almost3
area,3
crash3
yet.3
hosting3
machine3
That3
step3
kqueue3
haven't3
support3
collected3
sent3
Relic3
performance3
early3
collection3
affected3
poor3
level.3
gathered3
dig3
changes3
fetching3
user,3
believe3
breaks,3
fail3
affects3
matters3
however,3
got3
us3
favorite3
potential3
Working3
hard.3
scale3
something,3
getting3
though:3
installed3
services,3
were3
way.3
added3
likely3
Other3
breaks3
components3
finish3
necessarily3
later.3
delivering3
Here's3
all.3
dataset.3
again.3
serve3
causing3
state3
information3
enable3
accepting3
him3
I've3
say3
break,3
available,3
monitor3
SSH3
solely3
anyway.3
incidents3
fix3
Database3
required3
code.3
failure,3
around,3
model.3
initial3
simplest3
slow,3
again3
view3
measure3
folks3
help3
is.3
them,3
Even3
else3
knowledge3
multiple3
proper3
yield3
queue3
yet3
side3
hit3
gather3
Ganglia,3
index3
MySQL3
slightly3
far,3
mail3
execution3
we'll3
main3
now3
works.3
developer3
Server3
commercial3
gets3
configured3
those3
life3
switch3
right?3
deployment.3
send3
Are3
layer3
defined3
Google3
used.3
nicer3
later3
below.3
simple:3
break;3
timers3
loop.3
break.3
money3
paid3
uses3
once,3
default3
dealing3
it'd3
too.3
Ruby's3
fine3
managing3
day,3
great3
Without3
hard3
select3
Knowing3
hand,3
returns3
iteration3
three3
pay3
PDF3
Developers3
here's3
developers3
buying3
handling3
serving3
Learn3
available?3
works3
networking3
real3
Operations3
alert3
applications3
and/or3
email3
CouchDB,3
seems3
master3
hardware3
machines3
post3
implementation3
higher3
recent3
EC23
man3
above.3
events3
books3
API3

two word phrases repeated minimum three times

PhraseQuantity
to be34
in the27
of the25
your application25
on the25
you can20
to the18
in your18
need to17
the data16
the last16
able to15
from the15
is not15
with the13
and the13
all the13
the first12
your database12
lot of12
when you12
number of11
you have11
be able11
to know10
will be10
one of10
If you10
of your10
know what10
should be10
you to10
have to10
file descriptors9
that you9
to your9
When you9
needs to9
set of8
your application,8
the most8
it will8
bunch of8
to get8
want to8
for the8
to analyze8
the book8
some sort8
list of8
sort of8
the next8
call to7
more than7
at any7
you need7
of them7
or the7
you should7
kind of7
out of7
it to7
to do7
You should7
to find7
your application.7
data to7
all of7
you do7
of file7
which is7
of data7
if you7
is the7
couple of7
deal with7
of what7
to collect7
on your7
data is7
is to6
when the6
book is6
most important6
and it's6
may be6
case of6
to deal6
your code6
not be6
don't need6
the event6
You can6
based on6
the operating6
tools like6
you know6
operating system6
in turn6
it's the6
find out6
This is6
data from6
when it6
in place6
in this6
it's not6
to use6
you don't6
access to6
by Mathias5
is an5
you use5
2011 by5
that the5
kinds of5
Note that5
you get5
related to5
site is5
to look5
not just5
you want5
it makes5
it in5
the more5
the time5
be the5
at some5
into the5
and you5
shouldn't be5
Do you5
event loop,5
by the5
to not5
Posted on5
written to5
amount of5
Mathias Meyer5
when your5
open source5
the process5
to have5
for you.5
and then5
much more5
of all5
It's not5
and it5
it doesn't5
over the5
going to5
monitoring and5
look at5
give you5
you add5
and I'm5
not about5
your site5
to keep5
of failure.5
first time4
but in4
using the4
log files4
the list4
you write4
soon as4
the open4
you just4
the C++4
should know4
You don't4
all file4
know how4
file descriptors.4
you shouldn't4
Most of4
play with4
to play4
ready for4
don't have4
which in4
of it4
piece of4
track of4
doesn't have4
take care4
care of4
way of4
available to4
most of4
The more4
set up4
but it4
application server4
what happens4
be used4
your infrastructure4
is still4
one thing4
working on4
about the4
seem to4
the log4
and your4
and all4
read from4
of my4
the other4
with it4
get to4
that it's4
something that4
descriptors for4
the same4
that are4
it comes4
to add4
to an4
kill -94
that it4
process or4
to you,4
can and4
comes to4
where you4
tools available4
because it's4
part of4
to wait4
there's no4
an external4
and they4
like the4
and so4
over time,4
I'm not4
time you4
be sure4
the database4
it's just4
in place,4
what's going4
database queries4
as you4
an infrastructure4
There's no4
is that4
some of4
back to4
too much4
do with4
It should3
and to3
all your3
on some3
where it3
file descriptor3
it and3
keep an3
This way3
use it3
of metrics3
tools are3
for all3
going on3
you and3
time around.3
your data3
will fail3
skill set3
New Relic3
the user,3
at least3
through some3
get an3
it's much3
easier to3
last time3
to start3
used to3
could be3
how to3
for some3
data and3
this area3
and that3
is good3
enough to3
has been3
all things3
you'll be3
to tell3
your users3
is simply3
you kill3
affects your3
of handling3
to check3
external services3
to disk.3
or your3
it'd be3
never get3
right the3
the magic3
magic happens3
over time.3
metrics gathering3
and metrics3
data that3
application or3
you'll never3
at all,3
written in3
that will3
is usually3
In the3
do you3
the user3
hours to3
but also3
source tools3
allowing you3
running on3
for that3
of these3
wait for3
tell you3
so on.3
data when3
you when3
When your3
up to3
the number3
always have3
you go3
in that3
things that3
to you3
this is3
to run3
waiting for3
rely on3
one important3
an abundance3
collect and3
that may3
on every3
what it3
file and3
make it3
will usually3
is just3
on disk,3
just one3
the simplest3
come in3
can be3
log file3
happens when3
to automate3
abundance of3
of tools3
sense of3
false sense3
time to3
useful to3
easier it3
the easier3
allow you3
it was3
reason why3
to go3
and not3
are the3
your servers3
of code3
is ready3
they don't3
In case3
the problem.3
having to3
They can3
for you3
available on3
your own3
of an3
find the3
of log3
in my3
important to3
so far,3
poor guy3
an application3
the one3
to take3
can easily3
server process3
it for3
tools to3
not yet3
for both3
them is3
matter if3
the new3
it is3
is nothing3
on it3
level of3
activity in3
the case3
If your3
infrastructure, and3
with your3
as well3
for new3
new tools3
web server,3
first place.3
what kind3
setting up3
be aware3
get the3
There is3
SSH access3
for your3
the different3
on all3
tool to3
view of3
when it's3
your favorite3
installed on3
in general3
server, your3
that your3
it can3
bit more3
just like3
but your3
Whenever you3
seems to3
the available3
out to3
be available.3
application is3
as an3
at the3
the idea3
so it's3
pretty much3
you call3
event loop3
the current3
can throw3
as soon3
something out3
out there3
the world3
that can3
something you3
ensure that3
the final3
HTTP request3
the connection3
I'm currently3
as the3
the socket3
and when3
easy to3
trying to3
them to3

three word phrases repeated minimum three times

PhraseQuantity
be able to11
some sort of8
to deal with6
need to know6
in your application6
to be able5
by Mathias Meyer5
2011 by Mathias5
you need to5
it's not about4
don't need to4
you know what4
the most important4
the open source4
the first time4
take care of4
in the last4
Do you know4
the operating system4
your site is4
needs to be4
of file descriptors.4
which in turn4
You don't need4
what's going on3
kind of data3
to play with3
the easier it3
of the event3
as soon as3
based on the3
file descriptors for3
allowing you to3
the number of3
the list of3
and it will3
important to your3
monitoring and metrics3
the first place.3
you want to3
to find out3
of your application,3
with the new3
set of log3
application server process3
most of the3
open source tools3
the last time3
data from the3
false sense of3
number of file3
in the first3
allow you to3
be used to3
have to be3
SSH access to3
able to deal3
all file descriptors3
right the first3
to not be3
the event loop,3
one of the3
know how to3
You should know3
of file descriptors3
and so on.3
case of failure.3
in this area3
easier it will3
is that you3
know what happens3
it will be3
what kind of3
the magic happens3
an abundance of3

B tags

Search:

U tags

I tags

images

file namealternative text
Fork me on GitHub
Pingdom
New Relic
Munin

headers

H1

H2

Shameless Plug

H3

Shameless Plug

H4

Posted on 07 Sep 2011 by Mathias Meyer

Posted on 25 Jul 2011 by Mathias Meyer

Posted on 25 Apr 2011 by Mathias Meyer

Posted on 10 Jan 2011 by Mathias Meyer

Posted on 05 Jan 2011 by Mathias Meyer

H5

H6

internal links

addressanchor text
07 Sep 2011
me know
(view/add your own)
nosql
books
25 Jul 2011
operations
25 Apr 2011
ruby
eventmachine
networking
nodejs
10 Jan 2011
mongodb
databases
nosql
durability
05 Jan 2011
infrastructure
monitoring
<< Archives
Search
Imprint/Impressum

external links

addressanchor text
Fork me on GitHub
Mathias Meyer
Redcarpet
Albino
Prince XML
DocRaptor
me
Mathias Meyer
Scalarium
Heroku
Google Apps
dotCloud
Chef
Puppet
MCollective
Munin
Ganglia
New Relic
collectd
Nagios
PagerDuty
Monit
God
bluepill
supervisord
RUnit
Ostrich
Scout
two
part
Release It!
Web Operations: Keeping the Data on Time
Pragmatic Project Automation
The Art of Capacity Planning
Building Scalable Websites
High Performance MySQL, 2nd. Edition
How Complex Systems Fail
On Designing and Deploying Internet-Scale Services
Mathias Meyer
Scottish Ruby Conference
EventMachine
slides
EventMachine
libebb
rev
cool.io
libev
ext/rubymain.cpp
ext/cmain.cpp
EventMachine_t::Run()
_RunTimers()
connect()
Deferrables
em-http-request
select()
implementation
poll()
epoll
epoll_create
epoll_ctl
epoll_wait
read()
write()
em-synchrony
Goliath
TCP/IP Illustrated Vol. 1
Unix Network Programming
Mathias Meyer
tweeted two links
two
tweets
thread on the mailing list
http://learnmongo.com
Mathias Meyer
very fond of coffee
Scalarium
Pingdom
Hummingbird
New Relic
Request-log-analyzer
Exceptional
Hoptoad
Monit
God
Bluepill
runit
upstart
Scalarium
Munin
Nagios
Ganglia
collectd
CloudKick
Circonus
Scout
Scalarium
Flume
Scribe
Splunk
Loggly
Graylog2
logstash
PagerDuty
RSS Feed