- 03 Apr, 2018 1 commit
-
-
Ulan Degenbaev authored
This patch enables ShouldOptimizeForMemoryUsage if the old generation size is within 1/8th of the max old generation size. This patch also passes the reduce-memory flag to incremental marking whenever ShouldOptimizeForMemoryUsage is enabled. Bug: chromium:824214 Change-Id: I5cfc0566ca0e23dfa1b8c0439a4e67424ddc852d Reviewed-on: https://chromium-review.googlesource.com/973524 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#52333}
-
- 15 Mar, 2018 1 commit
-
-
Hannes Payer authored
Change-Id: I57da95525e09820ed1a1697cc4eb1e39ecb7c7cc Reviewed-on: https://chromium-review.googlesource.com/964282Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51961}
-
- 17 Jan, 2018 1 commit
-
-
Ali Ijaz Sheikh authored
Incremental marking job and concurrent marking tasks may be triggered during heap tear down. The task scheduler may already be torn down at this point. Avoid scheduling new tasks if tasks are disabled. Bug: v8:7238 Change-Id: I3869a20dc8b4f38b26754872448952a9aadb6bd9 Reviewed-on: https://chromium-review.googlesource.com/868825Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ali Ijaz Sheikh <ofrobots@google.com> Cr-Commit-Position: refs/heads/master@{#50641}
-
- 12 Oct, 2017 1 commit
-
-
Ulan Degenbaev authored
Bug: Change-Id: I9e4b2e1157f36dacb24f7a0d0c43d31c84de8488 Reviewed-on: https://chromium-review.googlesource.com/712397Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#48484}
-
- 22 Aug, 2017 1 commit
-
-
Ulan Degenbaev authored
Perf sheriffs: this is going to increase GC time in v8.runtimestats benchmarks. That time was not accounted before. Change-Id: I656aed7ec7f4fd9f29dd4a2eff44eb25a60f21ad Reviewed-on: https://chromium-review.googlesource.com/626636 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#47520}
-
- 21 Aug, 2017 1 commit
-
-
Michael Lippautz authored
Performance sheriffs: This CL adds better accounting and can thus cause regressions. Also-By: cbruni@chromium.org Bug: Change-Id: I38cdb702af201033e180741af40c4c5915553798 Reviewed-on: https://chromium-review.googlesource.com/623867Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#47476}
-
- 01 Aug, 2017 1 commit
-
-
Michael Lippautz authored
This makes all the information that is present for GCTracer also available to RCS. Bug: chromium:748569 Change-Id: Ie7e8c3770b81ab1321cad08f6954492b72ef0514 Reviewed-on: https://chromium-review.googlesource.com/585427 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#47043}
-
- 11 Jul, 2017 1 commit
-
-
Ulan Degenbaev authored
BUG=chromium:694255 Change-Id: Iaaa7a493bfad8817fba288efd486a5a7e8b0a0fb Reviewed-on: https://chromium-review.googlesource.com/567005 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#46560}
-
- 12 Jun, 2017 1 commit
-
-
hpayer authored
BUG=chromium:728228 Review-Url: https://codereview.chromium.org/2930333002 Cr-Commit-Position: refs/heads/master@{#45875}
-
- 04 May, 2017 1 commit
-
-
mlippautz authored
BUG=v8:6343 Review-Url: https://codereview.chromium.org/2860043002 Cr-Commit-Position: refs/heads/master@{#45079}
-
- 03 May, 2017 1 commit
-
-
mlippautz authored
BUG=v8:6343 Review-Url: https://codereview.chromium.org/2861763002 Cr-Commit-Position: refs/heads/master@{#45073}
-
- 05 Dec, 2016 1 commit
-
-
ulan authored
This reverts commit aea4f1a7. Reason: performance regression on benchmarks (crbug.com/671118). BUG=chromium:671118,chromium:613518 TBR=hpayer@chromium.org Review-Url: https://codereview.chromium.org/2549053002 Cr-Commit-Position: refs/heads/master@{#41479}
-
- 02 Dec, 2016 1 commit
-
-
ulan authored
BUG=chromium:613518 Review-Url: https://codereview.chromium.org/2407153002 Cr-Commit-Position: refs/heads/master@{#41459}
-
- 28 Sep, 2016 3 commits
-
-
ulan authored
Reland "[heap] New heuristics for starting of incremental marking. (patchset #9 id:160001 of https://codereview.chromium.org/2364923002/ )" This reverts commit a5440d11. BUG=chromium:616434 TBR=hpayer@chromium.org LOG=NO Review-Url: https://codereview.chromium.org/2379663002 Cr-Commit-Position: refs/heads/master@{#39838}
-
machenbach authored
Revert of [heap] New heuristics for starting of incremental marking. (patchset #9 id:160001 of https://codereview.chromium.org/2364923002/ ) Reason for revert: OOMs in nosnap debug: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/9572 Original issue's description: > [heap] New heuristics for starting of incremental marking. > > The motivation for this patch is to move more marking work to tasks. > This is done by postponing the start of incremental marking until > a marking task is running. > > This patch introduces a soft and a hard limits for incremental marking. > When the soft limit is reached, the marking task is scheduled. > If the hard limit is reached before the task is running, then > incremental marking is started without waiting for the task. > > BUG=chromium:616434 > LOG=NO > > Committed: https://crrev.com/55683ddd2a32e0dfb8df66271fbf53e3618cce9d > Cr-Commit-Position: refs/heads/master@{#39831} TBR=hpayer@chromium.org,ulan@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:616434 Review-Url: https://codereview.chromium.org/2375983002 Cr-Commit-Position: refs/heads/master@{#39833}
-
ulan authored
The motivation for this patch is to move more marking work to tasks. This is done by postponing the start of incremental marking until a marking task is running. This patch introduces a soft and a hard limits for incremental marking. When the soft limit is reached, the marking task is scheduled. If the hard limit is reached before the task is running, then incremental marking is started without waiting for the task. BUG=chromium:616434 LOG=NO Review-Url: https://codereview.chromium.org/2364923002 Cr-Commit-Position: refs/heads/master@{#39831}
-
- 12 Sep, 2016 1 commit
-
-
ulan authored
This patch changes incremental marking work scheduling from combination of idle/delayed tasks to ordinary short-running tasks and moves more marking work from V8.Execute to tasks by accounting how much bytes were marked in tasks. BUG=chromium:616434 LOG=NO Review-Url: https://codereview.chromium.org/2321553002 Cr-Commit-Position: refs/heads/master@{#39348}
-
- 07 Sep, 2016 1 commit
-
-
ulan authored
Now callers of Heap::CollectGarbage* functions need to specify the reason as an enum value instead of a string. Subsequent CL will add stats counter for GC reason. BUG= Review-Url: https://codereview.chromium.org/2310143002 Cr-Commit-Position: refs/heads/master@{#39239}
-
- 06 Sep, 2016 1 commit
-
-
ulan authored
This patch - extracts the logic of keeping track of allocated bytes from the actual incremental marking step. - replaces OldSpaceStep with a check for incremental marking start. - removes the force_marking parameter of AdvanceIncrementalMarking. BUG=chromium:616434 LOG=NO Review-Url: https://codereview.chromium.org/2304123003 Cr-Commit-Position: refs/heads/master@{#39213}
-
- 07 Apr, 2016 1 commit
-
-
hpayer authored
BUG=chromium:601204 LOG=n Review URL: https://codereview.chromium.org/1865333002 Cr-Commit-Position: refs/heads/master@{#35336}
-
- 04 Apr, 2016 1 commit
-
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1844293005 Cr-Commit-Position: refs/heads/master@{#35238}
-
- 24 Mar, 2016 1 commit
-
-
ulan authored
Based on CL 1777883002. BUG=chromium:590975 LOG=NO Review URL: https://codereview.chromium.org/1813963002 Cr-Commit-Position: refs/heads/master@{#35053}
-
- 14 Nov, 2015 1 commit
-
-
mlippautz authored
This change binds each {Cancelable} task to a so-called {CancelableTaskManager}, which is then used to handle concurrent cancelation as well as synchronizing shutdown for already running tasks. Since ownership of tasks is transferred to the platform executing a task (destructor), handling in the manager uses integer ids. Note that this also mitigates (modulo integer size) the ABA problem. All handling of {Cancelable} tasks is now encapsulated into the corresponding manager, which is instantiated for each isolate. R=hpayer@chromium.org BUG=chromium:524425 LOG=N CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg;tryserver.v8:v8_linux_gc_stress_dbg;tryserver.v8:v8_mac_gc_stress_dbg;tryserver.v8:v8_linux64_msan_rel;tryserver.v8:v8_linux64_tsan_rel;tryserver.v8:v8_mac64_asan_rel Review URL: https://codereview.chromium.org/1409993012 Cr-Commit-Position: refs/heads/master@{#31997}
-
- 26 Oct, 2015 1 commit
-
-
ulan authored
the memory reducer is enabled. BUG= Review URL: https://codereview.chromium.org/1419393002 Cr-Commit-Position: refs/heads/master@{#31554}
-
- 29 Sep, 2015 1 commit
-
-
mstarzinger authored
This prevents the internal incremental-marking.h to be usable outisde of the "heap" directory. The logic inside that component is only useful within the GC and is now properly encapsulated. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1374203002 Cr-Commit-Position: refs/heads/master@{#31010}
-
- 08 Sep, 2015 1 commit
-
-
ulan authored
This moves incremental marking steps from gc-idle-time-handler and heap to the new incremental marking task. BUG=chromium:490559 LOG=NO Review URL: https://codereview.chromium.org/1265423002 Cr-Commit-Position: refs/heads/master@{#30641}
-