From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] jsbg available for play
Date: Tue, 11 Jun 2019 07:21:21 -0400 [thread overview]
Message-ID: <20190511072121.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
I made the feature available to you-all, by the jsbg command, but I'm not optimistic about it.
It's complex, might have race conditions, could have even more if switched over to threads, and doesn't seem to speed things up in the simple tests I ran.
I make it available though because it does work on the server that Chris and I share, where curl uses openssl.
this generally has less problems across the board, and I wish my distro (fedora) did that but they don't (sigh).
So I guess it will work for most of you, and is worth playing with I guess.
When things are cached it really doesn't matter too much, which is why I did most of my tests with
cachesize = 0
which supresses caching.
In nasa, 3 of the 12 scripts are asynchronous, so if I implemented that, where you're not waiting for those three, it might speed up a bit.
I don't know; I'm gonna take a step back and chill for a bit.
Meantime, you might not want to dive into all sorts of threadwork unless you're convinced the feature really does help.
Karl Dahlke
reply other threads:[~2019-06-11 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190511072121.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/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).