- Jun 14, 2019
-
-
Linux Build Service Account authored
Change-Id: I0b03edb0cff501343e83b050929bb88669f3b0d0
-
- May 23, 2019
-
-
Change-Id: I8aa68077307f997726171cdf95c50eace6474087
-
- May 10, 2019
-
-
Change-Id: Icaf087228efd896da1be13952bb790fc76b0e753
-
Scott Lobdell authored
Change-Id: Ia6a166a28be718648315ae52c96e84dc657300b7
-
- May 09, 2019
-
-
Scott Lobdell authored
Change-Id: If15f415bf6551e092d4c5e90829cac2663054cdf
-
- May 04, 2019
-
-
android-build-team Robot authored
Change-Id: I861a9fbac2950dc0b55a0c8924589e1467def283
-
- May 03, 2019
-
-
Christopher Ferris authored
Bug: 131864803 Test: New bionic unit test to make sure that mallinfo and malloc_info match. Change-Id: Id2fd0c38106fa0150ff6baae538ecaea356296ec
-
- May 02, 2019
-
-
android-build-team Robot authored
Change-Id: If77c408963179195a24d2ea81a55db56091a0484
-
- May 01, 2019
-
-
Christopher Ferris authored
Removing the stats make the whole cache structure fit in a single page. Bug: 131362671 Test: Verified that all bionic malloc benchmarks are still the same. Test: It turns out that the malloc_sql benchmarks seem to get faster. Test: Verified that after this change, it saves about 2K PSS per thread. Change-Id: I4dcd633543f05f1a9d47db175f9977ddb42188a9 (cherry picked from commit a8b52518654725e64def5ebbd0ed472100e5a522)
-
- Apr 18, 2019
-
-
Change-Id: I9a92f90de0f4cd8584a741a6f28d934537e4841d
-
- Apr 11, 2019
-
-
Scott Lobdell authored
Change-Id: I8e5b958827e1735d098cd089c4f6135d63ac0c3a
-
- Apr 10, 2019
-
-
android-build-team Robot authored
Change-Id: Ifa1650339362606a727d133dedb6e17a987194ba
-
- Apr 09, 2019
-
-
Christopher Ferris authored
It was found that keeping just a few allocations of the same size around (even up to only 3) increases the allocation time significantly. This appears to be because I set the minimum tcache entries to 1. Removing this and the performance comes mostly all of the way back. There is still some loss, but probably just due to a different bin layout than jemalloc 4.x. This does increase the PSS slightly for many processes. About 1MB in my trace runs. However, it increases the performance of most multiple allocations by a factor of three. Bug: 129743239 Test: Ran memory_replay on all traces. Test: Ran new bionic benchmarks to verify things get better. Change-Id: Iff41d5b5002919c4df03fcb7d742e501f9e38b8e Merged-In: Iff41d5b5002919c4df03fcb7d742e501f9e38b8e (cherry picked from commit 0af4ee86dfa643feb786d659dbb219133c776a34)
-
- Apr 07, 2019
-
-
Change-Id: I80df1789cfcbcab7a8a1e86048c69608995fb020
-
- Apr 04, 2019
-
-
Scott Lobdell authored
Change-Id: I9e55cc58fb4751424711558b266af4c07f4b5892
-
android-build-team Robot authored
Change-Id: Ia0abdf81f7a0c3b58922f4a615a7508baf809905
-
- Apr 03, 2019
-
-
Bill Rassieur authored
am: 69a24699 Change-Id: Iefbbbefa572a090befc750ccea46ee8cbdc3c086
-
Change-Id: Icfec63c3d2d52ca8ad60897c0737fd5b30d1056f
-
- Mar 29, 2019
-
-
Bill Rassieur authored
Change-Id: I31e10da5bb3c0ee66b71a2f69c010acfaeeef6db BUG: 129345239
-
- Mar 26, 2019
-
-
Scott Lobdell authored
Change-Id: I62ff67062b6bddec75be0eed9bde91995ea96adc
-
- Mar 23, 2019
-
-
android-build-team Robot authored
Change-Id: I0cf4df8836f7a90160160fe81321ec609b32f098
-
Christopher Ferris authored
am: 766934fd Change-Id: Ic95f585264bf0b8ab7f75b8a04c04bc5ca779e17
-
Christopher Ferris authored
am: 08d6c0f8 Change-Id: I25764bf0f640d5cd24331b2dba9715860fdf4faf
-
Christopher Ferris authored
am: 46971b81 Change-Id: I2c52b0d542aa1c273857486d312675f63625a6dc
-
- Mar 22, 2019
-
-
Christopher Ferris authored
Bug: 124264835 Test: Ran bionic unit tests. Test: Ran dumpsys -t 6000 meminfo --unreachable of chrome process without Test: crashing. Change-Id: I2cc66e443fa278621b9878a888c74f38efcb79eb
-
- Mar 19, 2019
-
-
android-build-team Robot authored
Change-Id: I0712e24c754048581027078dc4dcce460b0be28f
-
Christopher Ferris authored
am: 27c2c8be Change-Id: I421cf23cfc8d2bb0280546c2217861ecc6d93f14
-
Christopher Ferris authored
am: b4e426ff Change-Id: I7cf232a3f365c7563ee96b415f898a1d6842254e
-
Christopher Ferris authored
am: cc374363 Change-Id: Ia44573af27aa921a31bd2e798066b43dc1d72d10
-
- Mar 18, 2019
-
-
Christopher Ferris authored
A jemalloc user reported that the best fit selection is causing them a memory leak. This code has been completely removed from the next release of jemalloc (5.2.0), so remove it since it doesn't have any real benefit. See https://github.com/jemalloc/jemalloc/issues/1454 Running the memory dumps, removing best fit appears to be a win: it is slightly faster and has the same PSS/VA. Bug: 128697497 Test: Ran jemalloc unit tests. Test: Ran memory dumps in 32 bit and 64 bit and observed that the PSS Test: and VA stayed the same, while run time improved slightly. Change-Id: I98a8ddf2cea837c8ade1afd4a998960c253d3932
-
- Mar 12, 2019
-
-
Change-Id: I80e9acda1512c2ca0f2859d1ba6732ebd6380496
-
- Mar 06, 2019
-
-
Change-Id: I792c39acc41a11f04622b105706cbdddbfc54e18
-
Scott Lobdell authored
Change-Id: I65c2e5fe62f241093a0a1540acc2d0f4f3aeba94
-
- Feb 26, 2019
-
-
android-build-team Robot authored
Change-Id: Ie7feb7d3f84f53604613d64f419d73d776271cec
-
- Feb 25, 2019
-
-
Xin Li authored
Bug: 126125118 Change-Id: I0485d2754a7a36d6b228f2926d2fc06e96a08c11
- Feb 21, 2019
-
-
Xin Li authored
Bug: 120848293 Change-Id: I38bf95211e9e25ff919ac7260cc7822bdaee7948
-
- Feb 20, 2019
-
-
Scott Lobdell authored
Change-Id: Ice755ff64a801691a8f2ab58b1dba59311f4b153
-
- Feb 17, 2019
-
-
android-build-team Robot authored
Change-Id: I15014b90403ce721de3b8e5a45b4c9abf835e4f8
-
- Feb 15, 2019
-
-
Dan Albert authored
am: 1078c77e Change-Id: I1b4d6abc8d7f3d2d2f1779edf66717f17cac4bd8
-