Basilisk: start browser = 331MB
Moderator: Basilisk-Dev
Re: Basilisk: start browser = 331MB
Give the details os bit type and other
My empty basilisk = 103mb on win8x32
By the way i use procexp , on the taskman it showed 72mb, poked basilisk for some time - procexp = 124 ; taskman still = 72
My empty basilisk = 103mb on win8x32
By the way i use procexp , on the taskman it showed 72mb, poked basilisk for some time - procexp = 124 ; taskman still = 72
Last edited by Fedor2 on 2018-05-02, 14:49, edited 2 times in total.
Re: Basilisk: start browser = 331MB
2-300 megs on startup sounds about right to load all the binary code for the program and all the support code from the operating system plus render the UI load the graphics and javascript to drive it plus extensions, their graphics and javascript etc.. What is the problem.. We live in a world where 4gbs is a minimum requirement overall for systems and generally 8gbs in a system is standard. I'd worry when it starts getting closer to a gig while nothing is loaded. This is 2018 after all not 1998.
Last edited by New Tobin Paradigm on 2018-05-02, 16:23, edited 2 times in total.
Re: Basilisk: start browser = 331MB
Not everyone in this world conforms to standard and software developers incorrectly assume the majority are using the "standard".Odd because i do not recall being asked what i use lol.New Tobin Paradigm wrote:2-300 megs on startup sounds about right to load all the binary code for the program and all the support code from the operating system plus render the UI load the graphics and javascript to drive it plus extensions, their graphics and javascript etc.. What is the problem.. We live in a world where 4gbs is a minimum requirement overall for systems and generally 8gbs in a system is standard. I'd worry when it starts getting closer to a gig while nothing is loaded. This is 2018 after all not 1998.
My basilisk uses approximately 250mb upon startup and more or less hovers around that figure.I do find it irritating that developers tend to cater for the platters of the "latest" hardware etc and the others get left by the wayside and it sadly seems to be coming a trend.
user of multiple puppy linuxes..upup,fossapup.scpup,xenialpup.....
Pale moon 29.4.1
Pale moon 29.4.1
Re: Basilisk: start browser = 331MB
2 things:
- A current-day web browser is much more alike a full-fledged game than your average desktop application. This is because people have pushed web browsers to handle all sorts of content (including games) internally. So, 300 MB on startup is not odd if your system provides all the knobs and buttons for the browser to initialize all systems; accelerated audio, video, a full javascript language compiler, html5, css3, webgl (3D graphics), etc. etc. the list goes on. Things also depend on what your home page is.
- Basilisk will use more memory if you have more available. So if you have 8GB in your system expect it to use considerably more than if you have 1GB available.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk: start browser = 331MB
I think 331MB upon startup is quite good. Really good.
What you should note is how your RAM usage change when you have, e.g. 10 tabs open. Compare Basilisk to something like Chrome and you'll soon see how amazing Basilisk is
What you should note is how your RAM usage change when you have, e.g. 10 tabs open. Compare Basilisk to something like Chrome and you'll soon see how amazing Basilisk is
Systemd Free - MX Linux, Antix Linux & Artix Linux
Re: Basilisk: start browser = 331MB
Not just Basilisk. Of the other in-development UXP applications I am seeing similar base nothing but its self loaded usage. Though, slightly less because Basilisk has a few more items than say Pale Moon 28 does.
That can be accounted for by subtracting inital commit of the binary code for webrtc all the operational glue for DRM and the overhead in the js area of Australis "CustomizableUI" plus the support JS of the WebExtensions translation framework.
That can be accounted for by subtracting inital commit of the binary code for webrtc all the operational glue for DRM and the overhead in the js area of Australis "CustomizableUI" plus the support JS of the WebExtensions translation framework.
Last edited by New Tobin Paradigm on 2018-05-03, 08:25, edited 2 times in total.