summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* nonmoving: Upper-bound time we hold SM_MUTEX for during sweepwip/gc/opt-pauseBen Gamari2019-10-221-1/+25
|
* nonmoving: Don't do two passes over large and compact object listsBen Gamari2019-10-221-10/+14
| | | | | | | | | | | Previously we would first move the new objects to their appropriate non-moving GC list, then do another pass over that list to clear their mark bits. This is needlessly expensive. First clear the mark bits of the existing objects, then add the newly evacuated objects and, at the same time, clear their mark bits. This cuts the preparatory GC time in half for the Pusher benchmark with a large queue size.
* nonmoving: Trace GC preparation stepsBen Gamari2019-10-221-0/+4
|
* rts: Mark nonmoving GC paths in moving collector as unlikelywip/gc/compact-nfdataBen Gamari2019-10-221-8/+8
| | | | | | The expectation here is that the nonmoving GC is latency-centric, whereas the moving GC emphasizes throughput. Therefore we give the latter the benefit of better static branch prediction.
* rts: COMPACT_NFDATA support for the nonmoving collectorÖmer Sinan Ağacan2019-10-2211-18/+139
| | | | | | This largely follows the model used for large objects, with appropriate adjustments made to account for references in the sharing deduplication hashtable.
*-. Merge branches 'wip/gc/segment-header-to-bdescr' and 'wip/gc/docs' into ↵wip/gc/everything2Ben Gamari2019-10-227-39/+253
|\ \ | | | | | | | | | wip/gc/everything2
| | * NonMoving: Add summarizing Notewip/gc/docsBen Gamari2019-10-223-1/+189
| | |
| * | NonMoving: Move next_free_snap to block descriptorwip/gc/segment-header-to-bdescrBen Gamari2019-10-226-12/+18
| | |
| * | NonMoving: Move block size to block descriptorBen Gamari2019-10-224-16/+31
| | |
| * | NonMoving: Introduce nonmovingSegmentLogBlockSize acccessorBen Gamari2019-10-223-14/+19
| |/ | | | | | | This will allow us to easily move the block size elsewhere.
* | NonMoving: Implement -xns to disable selector optimizationwip/gc/shortcuttingÖmer Sinan Ağacan2019-10-223-2/+13
| |
* | NonMovingMark: Handle INDs left by shortcuttingBen Gamari2019-10-221-2/+11
| |
* | NonMoving: Implement selector optimisationÖmer Sinan Ağacan2019-10-225-3/+353
| |
* | NonMoving: Implement indirection shortcuttingÖmer Sinan Ağacan2019-10-221-17/+47
|/ | | | | This allows indirection chains residing in the non-moving heap to be shorted-out.
*-. Merge branches 'wip/gc/optimize' and 'wip/gc/test' into wip/gc/everythingwip/gc/everythingBen Gamari2019-10-2221-233/+850
|\ \
| | * testsuite: Mark length001 as failing under nonmoving wayswip/gc/testBen Gamari2019-10-221-1/+1
| | | | | | | | | | | | This is consistent with the other unoptimized ways.
| | * testsuite: Don't run T7160 in nonmoving_thr waysBen Gamari2019-10-221-1/+1
| | | | | | | | | | | | The nonmoving way finalizes things in a different order.
| | * testsuite: Don't run T9630 in nonmoving waysBen Gamari2019-10-221-1/+3
| | | | | | | | | | | | The nonmoving collector doesn't support -G1
| | * Skip ghc_heap_all test in nonmoving waysBen Gamari2019-10-221-1/+2
| | |
| | * ghc-heap: Skip heap_all test with debugged RTSBen Gamari2019-10-221-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The debugged RTS initializes the heap with 0xaa, which breaks the (admittedly rather fragile) assumption that uninitialized fields are set to 0x00: ``` Wrong exit code for heap_all(nonmoving)(expected 0 , actual 1 ) Stderr ( heap_all ): heap_all: user error (assertClosuresEq: Closures do not match Expected: FunClosure {info = StgInfoTable {entry = Nothing, ptrs = 0, nptrs = 1, tipe = FUN_0_1, srtlen = 0, code = Nothing}, ptrArgs = [], dataArgs = [0]} Actual: FunClosure {info = StgInfoTable {entry = Nothing, ptrs = 0, nptrs = 1, tipe = FUN_0_1, srtlen = 1032832, code = Nothing}, ptrArgs = [], dataArgs = [12297829382473034410]} CallStack (from HasCallStack): assertClosuresEq, called at heap_all.hs:230:9 in main:Main ) ```
| | * testsuite: Skip T15892 in nonmoving_thr_ghcBen Gamari2019-10-221-1/+1
| | |
| | * testsuite: bug1010 requires -c, which isn't supported by nonmovingBen Gamari2019-10-221-1/+4
| | |
| | * testsuite: Ensure that threaded tests are run in nonmoving_thrBen Gamari2019-10-222-9/+13
| | |
| | * testsuite: Nonmoving collector doesn't support -G1Ben Gamari2019-10-221-1/+2
| | |
| | * testsuite: Don't run T15892 in nonmoving waysBen Gamari2019-10-221-3/+5
| | | | | | | | | | | | The nonmoving GC doesn't support `+RTS -G1`, which this test insists on.
| | * testsuite: Add nonmoving_thr_ghc wayBen Gamari2019-10-221-1/+4
| | | | | | | | | | | | This uses the nonmoving collector when compiling the testcases.
| | * testsuite: Add nonmoving_thr wayBen Gamari2019-10-221-3/+6
| | |
| * | Unconditionally flush update remembered set during minor GCwip/gc/optimizeBen Gamari2019-10-222-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | Flush the update remembered set. The goal here is to flush periodically to ensure that we don't end up with a thread who marks their stack on their local update remembered set and doesn't flush until the nonmoving sync period as this would result in a large fraction of the heap being marked during the sync pause.
| * | NonMoving: Clean mut_listBen Gamari2019-10-221-1/+121
| | |
| * | NonMoving: Don't do major GC if one is already runningBen Gamari2019-10-222-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we would perform a preparatory moving collection, resulting in many things being added to the mark queue. When we finished with this we would realize in nonmovingCollect that there was already a collection running, in which case we would simply not run the nonmoving collector. However, it was very easy to end up in a "treadmilling" situation: all subsequent GC following the first failed major GC would be scheduled as major GCs. Consequently we would continuously feed the concurrent collector with more mark queue entries and it would never finish. This patch aborts the major collection far earlier, meaning that we avoid adding nonmoving objects to the mark queue and allowing the concurrent collector to finish.
| * | NonMovingMark: Eliminate redundant check_in_nonmoving_heapsBen Gamari2019-10-221-16/+15
| | |
| * | NonMoving: Optimise allocator cache behaviorBen Gamari2019-10-222-24/+42
| | | | | | | | | | | | | | | Previously we would look at the segment header to determine the block size despite the fact that we already had the block size at hand.
| * | NonMoving: Prefetch segment headerBen Gamari2019-10-222-2/+8
| | |
| * | NonMoving: Pre-fetch during markBen Gamari2019-10-222-1/+55
| | | | | | | | | | | | This improved overall runtime on nofib's constraints test by nearly 10%.
| * | NonMoving: Fuse sweep preparation into mark prepBen Gamari2019-10-223-45/+25
| | |
| * | NonMoving: Inline nonmovingClearAllBitmapsBen Gamari2019-10-221-25/+10
| | |
| * | NonMoving: Prefetch when clearing bitmapsBen Gamari2019-10-221-0/+2
| | | | | | | | | | | | | | | Ensure that the bitmap of the segmentt that we will clear next is in cache by the time we reach it.
| * | rts: Add prefetch macrosBen Gamari2019-10-221-0/+4
| | |
| * | NonMoving: Optimize bitmap search during allocationBen Gamari2019-10-221-2/+14
| | | | | | | | | | | | | | | Use memchr instead of a open-coded loop. This is nearly twice as fast in a synthetic benchmark.
| * | NonMovingMark: Optimize representation of mark queueBen Gamari2019-10-222-13/+38
| | | | | | | | | | | | This shortens MarkQueueEntry by 30% (one word)
| * | NonMoving: Allocate mark queues in larger block groupsBen Gamari2019-10-222-4/+7
| | |
| * | NonMoving: Eliminate integer division in nonmovingBlockCountBen Gamari2019-10-221-4/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Perf showed that the this single div was capturing up to 10% of samples in nonmovingMark. However, the overwhelming majority of cases is looking at small block sizes. These cases we can easily compute explicitly, allowing the compiler to turn the division into a significantly more efficient division-by-constant. While the increase in source code looks scary, this all optimises down to very nice looking assembler. At this point the only remaining hotspots in nonmovingBlockCount are due to memory access.
| * | More comments for agingwip/gc/agingBen Gamari2019-10-221-5/+91
| | |
| * | Disable aging when doing deadlock detection GCBen Gamari2019-10-225-33/+66
| | |
| * | Nonmoving: Allow aging and refactor static objects logicBen Gamari2019-10-2210-81/+266
| |/ | | | | | | | | | | | | This commit does two things: * Allow aging of objects during the preparatory minor GC * Refactor handling of static objects to avoid the use of a hashtable
* | NonmovingCensus: Emit samples to eventlogwip/gc/instrumentationBen Gamari2019-10-2210-2/+69
| |
* | Allow census without live word countBen Gamari2019-10-222-16/+47
| | | | | | | | | | Otherwise the census is unsafe when mutators are running due to concurrent mutation.
* | rts/Eventlog: More descriptive error messageBen Gamari2019-10-221-2/+4
| |
* | rts: Introduce non-moving heap censusBen Gamari2019-10-224-0/+111
| | | | | | | | | | | | | | | | This introduces a simple census of the non-moving heap (not to be confused with the heap census used by the heap profiler). This collects basic heap usage information (number of allocated and free blocks) which is useful when characterising fragmentation of the nonmoving heap.
* | rts: Tracing support for nonmoving collection eventsBen Gamari2019-10-227-2/+134
|/ | | | | | | | | | | | | | | | | | | | | | | | | | This introduces a few events to mark key points in the nonmoving garbage collection cycle. These include: * `EVENT_CONC_MARK_BEGIN`, denoting the beginning of a round of marking. This may happen more than once in a single major collection since we the major collector iterates until it hits a fixed point. * `EVENT_CONC_MARK_END`, denoting the end of a round of marking. * `EVENT_CONC_SYNC_BEGIN`, denoting the beginning of the post-mark synchronization phase * `EVENT_CONC_UPD_REM_SET_FLUSH`, indicating that a capability has flushed its update remembered set. * `EVENT_CONC_SYNC_END`, denoting that all mutators have flushed their update remembered sets. * `EVENT_CONC_SWEEP_BEGIN`, denoting the beginning of the sweep portion of the major collection. * `EVENT_CONC_SWEEP_END`, denoting the end of the sweep portion of the major collection.
View Lorry Controller Status