Date: Thu, 26 Jul 2012 14:35:51 +0300 From: Aleksandr Rybalko <ray@freebsd.org> To: freebsd-embedded@FreeBSD.org, jasone@FreeBSD.org Cc: adrian@FreeBSD.org Subject: jemalloc vs old allocator Message-ID: <20120726143551.b2b0ce30.ray@freebsd.org>
next in thread | raw e-mail | index | archive | help
Hi, I believe what Jason Evans done many test before commit jemalloc, but made by myself simple test for embedded environment. And get following results: 1. old malloc: Sum of RSS of userland programs: 28544K sysctl vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 1 Disk Wait: 1 Page Wait: 0 Sleep: 19) Virtual Memory: (Total: 2372224K Active: 250316K) Real Memory: (Total: 18096K Active: 11392K) Shared Virtual Memory: (Total: 15824K Active: 5288K) Shared Real Memory: (Total: 2644K Active: 2408K) Free Memory: 2192K 2. jemalloc with MALLOC_PRODUCTION: Sum of RSS of userland programs: 21196K sysctl vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 1 Disk Wait: 1 Page Wait: 0 Sleep: 19) Virtual Memory: (Total: 2380988K Active: 257820K) Real Memory: (Total: 19048K Active: 12144K) Shared Virtual Memory: (Total: 16180K Active: 5392K) Shared Real Memory: (Total: 2664K Active: 2392K) Free Memory: 2440K I check it on DIR-632(Atheros AR7242 with 32M RAM) between 10-20 mins of uptime. Device behave identical in both cases. So if "something" new take more memory than before, that "something" is not a jemalloc :) P.S. Many thanks to Jason for such great job! WBW -- Aleksandr Rybalko <ray@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120726143551.b2b0ce30.ray>