Fortunately, that’s simple: just cat a large file and measure the time it takes. So if you want to have results you can trust, you have to redo the benchmark on your machine. I suspect that both the linux scheduler and the X scheduler has a lot to say in this issue too. As some have told me, they get a quite different performance behavior on their system. UPDATE: Of course, the answer is actually not so simple. If you are low on memory, use wterm, rxvt, or Eterm. We show that congestion, start time and route through the terminal together are good predictors of turnaround time, leading to adequate predictive performance.If you want speed, use gnome-terminal or konsole.So, what is the best terminal? The answer is actually quite simple: Only aterm but without buffer comes with 6.5 MB pretty close.Įterm is quite fast and memory efficient (9 MB), even with transparency. Each instance requires only about 6.3 MB of RAM, even with 10.000 lines of buffer.
Wterm is both reasonably fast and the most memory efficient of all tested terminals. While it is probably the most widely used term, the only slower terminal is Microsoft Window’s cmd.exe! Each instance requires 16 MB RAM, which is a lot in comparison to other terms with similar features. When opening multiple terminals and each one with 10.000 lines of used buffer, each terminal requires about 16 MB, so when you open more than three terminals at once you have already lower memory requirements than when using konsole. This one instance requires about 45 MB freshly started. When you open multiple terminals, they are all memory managed from one gnome-terminal instance. Gnome-terminal has a very different memory behavior. When setting the history buffer to 10.000 lines, it increases to 38MB per instance. By using measured data of total 30 existing ones. Konsole uses a lot of memory, about 32 MB. benchmark metrics to investigate the energy performance of existing and future airport terminal buildings. If you compile a lot or have other automatically generated output, gnome-terminal and konsole are the clear winners.
This is a clever trick and has the advantage of being extremely fast, because not every letter needs to be pumped through the X windowing system. They buy the speed with quite a bit of memory consumption, and it can be clearly seen that the output does not smoothly scroll but only updates several times per second. Runtime in seconds timed with time cat rfc3261.txt Resultsīoth gnome-terminal and konsole are exceptionally fast, it takes only 0.25 to 0.59 seconds to display the 647976 bytes large file.
#BENCHMARK CPU TERMINAL PDF#
Without further ado, I give you the results (click here for a better readable PDF version):
0 kommentar(er)
