[Development] Assistant WebKit/WebEngine support

Kirill Burtsev kirill.burtsev at qt.io
Wed Jun 26 14:44:45 CEST 2019


Hi,

sorry, but that is not a right way to assess thing like memory consumption.

Windows shows in a task manager just private memory (can not be used
by other processes) usage for process. And that is really takes 15-20 Mb
but just for separate renderer process. Main process (in case for example
simplebrowser or minimal) needs around 30Mb of its own private memory
and +5Mb for every renderer process (basically page by default).
And there is also shared memory for all these processes (library itself,
which is over 100Mb for webengine, and other resources): 40Mb for main
process itself and then it goes to 80-90 with spawned rendereres. One can
see all these numbers inside extended columns for shared/private/workingset
memory inside detailed tab of a 'Task Manager', 'Resource Monitor' builtin
tools or simple ProcessHacker guitool for Windows.

So, for example, in case of offline html version of cppreference doc for c++:
https://en.cppreference.com/w/Cppreference:Archives
with 6 pages opened for basic_ostream it takes about this amount of memory:
30 + 6 * 5 + 15 * 6 + 80 = 230Mb

Single process mode will make it a little bit better but still in a hundreds range.

Btw, those who interested in displaying simple html pages with webengine
and its memory costs could look at a practical application inside KDE:
'System Monitor' builtin tool there for looking at system processes and stats
uses QtWebEngine by displaying simple fancy looking html for
'Detailed Memory Information' for every process.

Regard


________________________________________
From: Development <development-bounces at qt-project.org> on behalf of Simon Hausmann <Simon.Hausmann at qt.io>
Sent: Wednesday, June 26, 2019 13:47
To: Michal Klocek; development at qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support

Hi,

>From my earlier email:

    " I measured on Windows with a Qt Creator built with
WebEngine support and surfed a little through the docs. The memory
consumption of the web engine process weighed in between 14-20 MB of RAM."

That number came from the task manager in Windows.

Simon
________________________________
From: Development <development-bounces at qt-project.org> on behalf of Michal Klocek <michal.klocek at qt.io>
Sent: Wednesday, June 26, 2019 13:31
To: development at qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support

Could you explain how did you measure web engine memory consumption to
get 14-20MB of ram ?

On 6/26/19 1:12 PM, Simon Hausmann wrote:
>
> Am 25.06.19 um 23:53 schrieb Konrad Rosenbaum:
>> Option 4: convert to WebEngine
>> Pros: looks great; currently supported browser engine, only little
>> porting work
>> Cons: horrible memory footprint; acute terminal featuritis; adds lots of
>> dependencies (disqualifies it for most/many people redistributing it);
>> does not work on all platforms supported by Qt (makes assistant less
>> useful or even useless to those users); embedding in IDEs becomes much
>> more difficult (dependencies and #ifdef's for unsupported platforms)
>
>
> I'd really like to eliminate this myth of a "horrible memory footprint".
> I sent an email earlier in this thread regarding this and presented
> numbers that suggest otherwise for documentation content.
>
>
>
> Simon
>
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
>
_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development


More information about the Development mailing list