From: Geoff McLane <ubuntu@geoffair.info>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] showscripts()
Date: Thu, 21 Sep 2017 02:33:54 +0200 [thread overview]
Message-ID: <60cb60ff-196e-e089-be3d-cfea47622383@geoffair.info> (raw)
In-Reply-To: <20170820093813.eklhad@comcast.net>
> if it adds 100K ... removes 100K ... no gain.
Understood...
Well for windows zlib would still be a good choice... just add
find_package( ZLIB ), like the present find_package( Tidy ), etc, in
CMakeLists.txt, since at lease most Windows developers are very, VERY
likely to have ZLIB installed, as it is needed for a **lot** of projects...
And already have to setup the PATH to include other DLL's, like CURL...
to run eb...
But also understand this is not high priority... and actually
compression would certainly add a lot of other wrinkles, that may not be
worth the effort... and in Windows, a large EXE footprint, and
allocating lots of memory is the norm, and Windows handles it well...
Just for information, the eb Windows Release EXE is 1.9 MB, the Debug is
3 MB, plus 3.3 MB pdb, and 1.1 MB ilk files... and on loading the
nasa.gov site, using the MSVC debugger, shows some 67 MB of process
memory used, and takes about 3.5 minutes to load, using about 25% of the
CPU power, like 1 core, before falling to 0, waiting for the next
input... relatively quite a light-weight app compared to some I play
with...
So do not see any concern about eb memory usage... in Windows at
least... so shaving 50-100 K likewise does not seem worth the effort...
Regards, Geoff.
next prev parent reply other threads:[~2017-09-21 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 2:38 Karl Dahlke
2017-09-19 17:58 ` Geoff McLane
2017-09-19 19:31 ` Karl Dahlke
2017-09-20 23:32 ` Geoff McLane
2017-09-20 23:56 ` Dominique Martinet
2017-09-23 23:40 ` Kevin Carhart
2017-09-20 23:59 ` Kevin Carhart
2017-09-21 1:56 ` Karl Dahlke
2017-09-20 13:38 ` Karl Dahlke
2017-09-21 0:33 ` Geoff McLane [this message]
2018-01-30 15:41 Karl Dahlke
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=60cb60ff-196e-e089-be3d-cfea47622383@geoffair.info \
--to=ubuntu@geoffair.info \
--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).