[
https://issues.apache.org/jira/browse/TS-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901559#comment-14901559
]
James Peach commented on TS-3918:
---------------------------------
OK, here's my proposal.
1. Add a command-line option to {{traffic_server}} to disable free lists. If
this is given, then the class allocators are backed by malloc(3) rather than
the global free lists.
2. There is no separate configuration for this, you would just do
{code}
CONFIG proxy.config.proxy_binary_opts STRING "-M --disable_freelist"
{code}
3. Since there's no convenient way to separately control the per-thread proxy
allocators, I propose that we always use these. If you don't want per-thread
caches, you can set {{proxy.config.allocator.thread_freelist_size}} and
{{proxy.config.allocator.thread_freelist_low_watermark}} to 0.
4. The {{--disable-freelist}} build option would be removed.
> runtime option to disable freelists
> -----------------------------------
>
> Key: TS-3918
> URL: https://issues.apache.org/jira/browse/TS-3918
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration, Core
> Reporter: James Peach
> Assignee: James Peach
> Fix For: sometime
>
>
> Disabling the free list is helpful for debugging and could also be useful for
> memory-constrained deployments. Make this a run-time option (will require a
> {{traffic_server}} restart).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
