#489 Investigate adding TRIM_FASTBINS for DS compilations
Closed: wontfix 7 years ago Opened 11 years ago by mreynolds.

TRIM_FASTBINS is another option like using:

mallopt(M_MXFAST, value);

But it is set at compile time, and can not be changed unless you rebuild the server.

See ticket 386 for more info:

https://fedorahosted.org/389/ticket/386


TRIM_FASTBINS is supposed to work like MXFAST. Supposedly it doesn't take as much of a performance hit, while still reducing the memory footprint.

define TRIM_FASTBINS 1

Metadata Update from @mreynolds:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.4 backlog

7 years ago

I don't think this is needed. We have better ways to approach this, like getting rid of null space in pblock and others.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to review
- Issue close_status updated to: None

7 years ago

Metadata Update from @firstyear:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/489

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: invalid)

3 years ago

Login to comment on this ticket.

Metadata