Memory and Time results.



I present some interesting numbers regarding startup times and memory footprints. This started as a simple list but grew and expanded as raster pushed me along. I really only needed a little bit of data for my Uni assignment to put in a CSS table. It’s now a fairly comprehensive test. These results come from my system, with a slight bit of tweaking to make all the environments used to my liking, yet quite minimal. Results obviously vary from system to system and this is the raw results I found on my system. Your results may differ. (Now with shiny graphs!)



Mem base: Used Mem – Used Buffers&Cache
Mem user: Same with Chrome + Xterm loaded
Time: Time from boot to loaded environment. +/- 0.2 secs
Mem Base Comp: Total memory usage – (X11 + Xterm) memory usage
Time Base Comp: Boot time – Base Boot Time

X11 + Xterm
Mem base: 438792 – 231104 = 207.688 mb
Time: 19.8 secs

Mem base: 459368 – 245360 = 214.008 mb
Mem user: 627860 – 348424 = 279.436 mb
Time: 21.4 secs
Mem Base Comp: 6.32 mb
Time Base Comp: 1.6 secs

Mem base: 556552 – 306304 = 250.248 mb
Mem user: 746440 – 435060 = 311.380 mb
Time: 26.4 secs
Mem Base Comp: 42.56 mb
Time Base Comp: 6.6 secs

Mem base: 445740 – 232680 = 213.060 mb
Mem user: 611544 – 341940 = 269.604 mb
Time: 21.8 secs
Mem Base Comp: 5.372 mb
Time Base Comp: 2.0 secs

Mem base: 652904 – 370628 = 282.276 mb
Mem user: 809520 – 470540 = 338.980 mb
Time: 32.1 secs
Mem Base Comp: 74.588 mb
Time Base Comp: 12.3 secs

KDE Software Compilation® 4.3.2
Mem base: 1032896 – 650124 = 382.772 mb
Mem user: 1197904 – 753468 = 444.436 mb
Time: 35.9 secs
Mem Base Comp: 175.084 mb
Time Base Comp: 16.1 secs

*** Each environment was slightly tweaked to make it
more user friendly and usable. They are all very close
to being a default setup. GDM auto-login was used.
64bit Ubuntu 9.10 system with KDE,Gnome,Flux all from
the default repos.***


3 Responses to “Memory and Time results.”

  1. 1 jxn

    This is _really_ with ubuntu 9.1 and GDM? Ever since installing 9.10 (as opposed to most other variants) login time is SSSSSLLLLOOOOOOWWWWW for me on ubuntu with any DM. That brown post-login loading screen lingers for 15 seconds or so no matter what–long after Enlightenment is loaded–and I don’t know how to get rid of it.

    I know this, because for a while I experimented with the openGeu variant, which includes comp manager which disables that brown screen, and e17 loaded in one or two seconds!

    Did you do anything special to get rid of the loading screen? Or does it not show up with autologin (can’t use that on my multiuser system)?

    • 2 edjy

      YES I did get rid of that stupid login screen. Im pretty sure it was ‘sudo apt-get remove xsplash’ did the trick. I also disabled usplash but because theres no point loading a splash screen when the whole system is up in 12 secs.

  2. To all Enlightenment Users and Developers,

    this post presents the simple idea of bringing two great projects together, namely to create a flagship distribution for Enlightenment based on Tiny Core Linux.

    “Tiny Core Linux is a very small (10 MB) minimal Linux GUI Desktop. It is based on Linux 2.6 kernel, Busybox, Tiny X, and Fltk. The core runs entirely in ram and boots very quickly. Also offered is Micro Core a 6 MB image that is the console based engine of Tiny Core. CLI versions of Tiny Core’s program allows the same functionality of Tiny Core’s extensions only starting with a console based system.
    It is not a complete desktop nor is all hardware completely supported. It represents only the core needed to boot into a very minimal X desktop typically with wired internet access.
    The user has complete control over which applications and/or additional hardware to have supported, be it for a desktop, a netbook, an appliance, or server, selectable by the user by installing additional applications from online repositories, or easily compiling most anything you desire using tools provided.”

    The goal of Tiny Core Linux is the „creation of a nomadic ultra small desktop capable of booting from cdrom, pendrive, or frugally from a hard drive. The desktop boots extremely fast and is able to support additional applications and hardware of the users choice. While Tiny Core always resides in ram, additional applications extensions can either reside in ram, mounted from a persistent storage device, or installed into a persistent storage device.“

    We believe that a cooperation between both projects would greatly facilitate the develpement of both and could result in a new and exciting distribution.

    Please feel free to share your ideas and comments on the TCL forum:

    Existing posts related to E:

    The idea:



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: