[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] configure: Add support for jemalloc
From: |
Alexandre DERUMIER |
Subject: |
Re: [Qemu-devel] [PATCH] configure: Add support for jemalloc |
Date: |
Tue, 23 Jun 2015 11:10:47 +0200 (CEST) |
>>You can try using or modifying this systemtap script:
Thanks, I'll check this.
If it can help, I have done a small top of qemu libc vs jemalloc vs tcmalloc
libc-2.19.so
-------------
started
-------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5294 root 20 0 26.953g 596744 18468 S 1.0 0.2 0:16.81 qemu
fio running (200kiops)
----------------------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5294 root 20 0 30.373g 633300 18552 S 2053 0.2 9:37.03 qemu
jemalloc
--------
started
--------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1789 root 20 0 11.640g 609224 18812 S 1.0 0.2 0:21.03 qemu
fio running (300kiops)
----------------------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1789 root 20 0 12.868g 684924 19144 S 2689 0.3 4:57.96 qemu
tcmalloc (16MB)
---------------
started
-------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1789 root 20 0 11.640g 609224 18812 S 1.0 0.2 0:21.03 qemu
fio running (65k iops)
-------------------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6900 root 20 0 10.925g 643624 18432 S 1125 0.2 4:18.51 qemu
tcmalloc (256MB)
---------------
started
-------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10640 root 20 0 10.117g 584524 18236 S 0.7 0.2 0:16.28 qemu
fio running (200k iops)
-----------------------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10640 root 20 0 10.983g 685136 18984 S 2566 0.3 12:34.73 qemu
----- Mail original -----
De: "pbonzini" <address@hidden>
À: "aderumier" <address@hidden>
Cc: "qemu-devel" <address@hidden>
Envoyé: Mardi 23 Juin 2015 10:57:03
Objet: Re: [PATCH] configure: Add support for jemalloc
On 23/06/2015 10:22, Alexandre DERUMIER wrote:
> > What is the peak memory usage of jemalloc and tcmalloc?
>
> I'll try to use an heap profiling to see.
> Don't known if "perf" can give me the info easily without profiling ?
You can try using or modifying this systemtap script:
https://sourceware.org/systemtap/examples/process/proctop.stp
Paolo