edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] stackoverflow and css
Date: Sun, 11 Feb 2018 18:08:46 -0500	[thread overview]
Message-ID: <20180111180846.eklhad@comcast.net> (raw)
In-Reply-To: <20180211194301.gx6i6nago4ietkxo@toaster>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

It's worse than we thought.
I always like to build a local test.
Download www.eklhad.net/csstest.zip and review.

over.css: the selectors from stackoverflow.com, this is their css file.
csstest: the file to browse.

Browse with db3 of course.
eb$qs$start comes back in jig time, which suggests the slowdown is in traversing and testing all the nodes, not in the parsing.
This test file only has 6 nodes, as shown by dumptree(document).
Problems listed below.

1. There is a syntax error.
Their software doesn't allow a classname to start with a dash, and yet it can, I guess.
You see the syntax error with db3.

2. Their program stops at the first error. So it only did part of the list.

3. This error occurs at 471, out of 3198.
If it had gone all the way through, on stackoverflow.com, this routine would take 2 times 3198 / 471 = 13.5 minutes.
So we can rightfully think of a 13.5 minute startup cost just to browse this site.
Obviously we can't live with that.

There are so many issues I almost think we should rewrite it from scratch, either in C or js.
Obviously I'd use theirs as a guide, but lordy! IDK

Karl Dahlke

      parent reply	other threads:[~2018-02-11 23:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 18:53 Karl Dahlke
2018-02-11 19:25 ` Adam Thompson
2018-02-11 19:43   ` Adam Thompson
2018-02-11 21:03     ` Karl Dahlke
2018-02-11 21:24     ` Karl Dahlke
2018-02-13 19:05       ` Adam Thompson
2018-02-11 23:08     ` Karl Dahlke [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=20180111180846.eklhad@comcast.net \
    --to=eklhad@comcast.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).