From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] why is nasa slow
Date: Sat, 23 Sep 2017 03:19:47 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709230314490.22113@carhart.net> (raw)
In-Reply-To: <20170823054132.eklhad@comcast.net>
> We should also ask why nasa is so crazy slow, 1.5 minutes to browse, how long does it take in another browsers?
This isn't a complete answer but when I run with db5, it noticeably sits
still, adding to the delay, with nothing being logged, right after kill
tag 333:
kill tag object 340
gc 0x38546c8
kill tag text 337
gc 0x3854758
kill tag object 335
gc 0x3807de8
kill tag object 333
And then when picks up and logs more stuff, it's calling fetchHTTP about
six or seven times. The log says "xhr1", "xhr2" etc.
I don't know what that means for where it is in the edbrowse run, but
does this tell you where it is?
prev parent reply other threads:[~2017-09-23 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170823054132.eklhad@comcast.net>
2017-09-23 10:14 ` [Edbrowse-dev] Caroline, different Kevin Carhart
2017-09-23 12:12 ` Karl Dahlke
2017-09-23 12:30 ` Karl Dahlke
2017-09-24 0:05 ` Kevin Carhart
2017-09-23 10:19 ` Kevin Carhart [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.03.1709230314490.22113@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
/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.
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 NNTP newsgroup(s).