btw, how was memory consumption measured? ps aux? free? a different way to completely fail?
Announcement
Collapse
No announcement yet.
Power & Memory Usage Of GNOME, KDE, LXDE & Xfce
Collapse
X
-
Originally posted by yotambien View PostTHE FIVE STAGES OF BENCHMARK LOSS
Stage 1: SHOCK
The first reaction when you see an article, scanning down to see your competition wipe the floor with you.
Typical postings: 'WTF', 'no way', 'you lie'...
..clipped...
Comment
-
Originally posted by << ⚛ >> View PostI don't agree with those slides made by Michael Larabel&co. They are implying that Larabel is always right and benchmark critics are always wrong. That's a completely ridiculous implication.
The point is that the benchmarks are just what they are. Benchmarks.
The numbers are just what they are, numbers.
I believe that within this thread *NOONE* has gone through and reproduced *EXACTLY* what Michael did for the article. mugginz came close, and guess what, he was in a similar order.
The majority of this thread is about people arguing their side of the coin, or saying that their figures don't match up. As mentioned in the presentation, and mentioned elsewhere.
Feel free to standup and do the following
1) Reproduce the test and the results
2) Make suggestions for improvements or clarifications
3) Present a similar set of results with the modified methodology.
But I don't think I have seen anyone get past 1). No one has voting rights for 2 or 3 unless you do 1.
You just confessed that you put those excerpts there without actually understanding them. Nice.
Regards,
Matthew
Comment
-
Got bored and wrote some automated bench scripts.
First lot off the press.
Bench procedure: (Chart 1)- Clean install from standard ISO of Kubuntu Karmic 9.10 (no updates)
- Apply the bench script and video file to the install just after installation procedure and before machine is booted.
Note: Numbers for Run 1 represents the first time that image has ever been booted. - The machine is booted. Bench script is auto-run on each boot.
- Bench runs and when finished auto reboots machine, etc.
- Once 5 loops of Boot-Bench-Reboot occur, metrics are stored to another machine.
After the fifth run of the first group, the bench script stops and all updates are applied. (Standard repos)
Bench procedure: (Chart 2)- The machine is booted. Bench script is auto-run on each boot.
Note: Numbers for Run 1 represents the first time that image has been booted since updates were applied. - Bench runs and when finished auto reboots machine, etc.
- Once 5 loops of Boot-Bench-Reboot occur, metrics are stored to another machine.
The contents of the benchmark are as follows:- Autostart on boot recording RAM usage once every second for 20 seconds.
- Launch Konsole and record RAM usage once every second for 20 seconds.
- Quit Konsole via dbus and record RAM once usage every second for 20 seconds.
- Launch Dragon Player with ogg theora video and record RAM usage once every second for 20 seconds.
(Dragon Player is the default video playback program for Kubuntu 9.10) - Quit Dragon Player via dbus control and record RAM usage every second for once 20 seconds.
- Reboot the machine.
Interestingly the machine never saw more than 267M used if you dont include the first run after installation or updates (Run 1 for both Charts)
These numbers are for x64 installs and KDE 4.3
The next run will be for Ubuntu 10.04 Gnome x64.
Comment
-
Originally posted by mugginz View PostYou must of read my mind.
But it's good to see the Analysis stage under-way (and hey, you started around post 30 or so .
Comment
-
Originally posted by mtippett View PostThere are some gaps. What resolution movie, screen, graphics driver, etc. The first run vs consequent run is intriguing - maybe data coversion/loading.
But it's good to see the Analysis stage under-way (and hey, you started around post 30 or so .
Complete specs as per prev post a while back.
1024M RAM
8G Storage
Gfx Driver for Cirrus Logic 5446
The movie was the demo ogg file from the Wikipedia site for Theora. I-15bis.ogg It's a 1:40 video but my script terminates playback after 20s via dbus so as to do a clean quit as per what a user might do.
Resolution of video is 320x240 25 f/s
Screen is set at 1024x768 so as to have 24bit/pixel (a limitation of the gfx card emulated)
All parameters of tests will be held consistent between machines.
Only the OS, Desktop, and hardware will change in order to see what happens for different PC configs.
Comment
-
WHY THE MEMORY TEST RESULTS ARE WRONG
Nobody needs to discuss the memory results as they are just wrongly calculated. The source is:
Search for USED. It parses the output of
Code:free -t -m 2>&1
Code:free -t -m 2>&1 total used free shared buffers cached Mem: 1977 1231 746 0 345 359 -/+ buffers/cache: 526 1451 Swap: 0 0 0 Total: 1977 1231 746
You get the htop value (which is correct) using:
Code:free -m|awk '/Mem/{print $3-$6-$7}'
Code:echo $((($(awk '/MemTotal/{print $2}' /proc/meminfo)-$(awk '/MemFree/{print $2}' /proc/meminfo)-$(awk '/Buffers/{print $2}' /proc/meminfo)-$(awk '/^Cached:/{print $2}' /proc/meminfo))/1024))
Comment
-
Corrected source link, could not edit it...
Comment
Comment