|Anonymous | Login | Signup for a new account||2014-04-18 15:09 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006294||OCaml||OCaml runtime system||public||2014-01-13 14:01||2014-01-17 17:50|
|Target Version||Fixed in Version|
|Summary||0006294: Poor tracking of extra heap resources|
|Description||Currently, when a custom block is allocated, the caller passes an arbitrary ratio between 0 and 1. This ratio is added to the caml_extra_heap_resources accumulator. Each time the accumulator reaches 1, a garbage collection is triggered and the accumulator is reset to 0.|
This "feature" is breaking the usability of Why3ide badly. Consider the following numbers obtained by launching Why3ide on a large testcase.
946.39user 0.36system 16:13.65elapsed 97%CPU (0avgtext+0avgdata 658164maxresident)k
As you can, it takes mote than 16 minutes before the user can interact with the program. Most of the time is wasted in the garbage collector. If we disable the accumulator, we get the following numbers:
18.98user 0.41system 1:26.67elapsed 22%CPU (0avgtext+0avgdata 761232maxresident)k
Now it takes only 19 seconds for the program to start. That is a x50 speedup!
By the way, this might seem like a degenerate case. But even on smaller testcases, the speedup is noticeable by the user, since each user interaction was triggering a major collection before.
The blame is not solely on OCaml. My opinion is that this is misfeature of OCaml that is misused by Lablgtk, leading to a disastrous user experience when using Labgtk-based applications.
Follow this link if you want to see how we disabled this part of the GC without having to ask our users to recompile OCaml:
|Tags||No tags attached.|
This is a very interesting test case.
I had already noticed slow behavior when using lablgtk from the top-level, but not in standalone applications.
I agree that this is a bad situation, but what you are doing is just disabling the feature.
This is going to work if your program triggers the GC by itself (i.e. if it allocates sufficiently in the heap), but not if it is doing only user interaction without allocating (or allocating very little).
We do not want to run out of extra-heap resources in that case.
I think we need a new approach, but I'm not sure what.
One possibility would be not to trigger the GC when the accumulator reaches 1, but rather to wait some amount of time before doing it (if it doesn't happen before). This would reduce the significance of the fraction, which is almost impossible to choose correctly.
I don't think the GC needs to do anything about it. As you say, the fraction is impossible to choose correctly, which makes the mechanism kind of pointless. If the GC needs to be run regularly, it doesn't have to be up to the GC to do it, it might just as well be done by the user program (especially if it is an interactive one).
Ideally, there should be a way to tell the actual footprint of each custom block and the threshold at which point a collection should start. (I thought that was already possible; I must have been mistaken.) Note that this can be accurately emulated in the user space thanks to a global accumulator and some finalizer functions. I guess it would be cheaper in the GC though, since no finalizer would be needed then.
> Ideally, there should be a way to tell the actual footprint of each custom block and the threshold at which point a collection should start.
Probably per resource type?
On a side note, bindings should provide the way to explicitely destroy the expensive resources..
|2014-01-13 14:01||gmelquiond||New Issue|
|2014-01-15 14:56||garrigue||Note Added: 0010801|
|2014-01-15 14:56||garrigue||Assigned To||=> garrigue|
|2014-01-15 14:56||garrigue||Status||new => feedback|
|2014-01-15 17:15||gmelquiond||Note Added: 0010802|
|2014-01-15 17:15||gmelquiond||Status||feedback => assigned|
|2014-01-16 03:37||ygrek||Note Added: 0010803|
|2014-01-17 17:50||doligez||Relationship added||related to 0006133|
|Copyright © 2000 - 2011 MantisBT Group|