Backport from sid to buster
[hcoop/debian/mlton.git] / doc / guide / localhost / RunningOnFreeBSD
CommitLineData
7f918cf1
CE
1<!DOCTYPE html>\r
2<html lang="en">\r
3<head>\r
4<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">\r
5<meta name="generator" content="AsciiDoc 8.6.9">\r
6<title>RunningOnFreeBSD</title>\r
7<link rel="stylesheet" href="./asciidoc.css" type="text/css">\r
8<link rel="stylesheet" href="./pygments.css" type="text/css">\r
9\r
10\r
11<script type="text/javascript" src="./asciidoc.js"></script>\r
12<script type="text/javascript">\r
13/*<![CDATA[*/\r
14asciidoc.install();\r
15/*]]>*/\r
16</script>\r
17<link rel="stylesheet" href="./mlton.css" type="text/css">\r
18</head>\r
19<body class="article">\r
20<div id="banner">\r
21<div id="banner-home">\r
22<a href="./Home">MLton 20180207</a>\r
23</div>\r
24</div>\r
25<div id="header">\r
26<h1>RunningOnFreeBSD</h1>\r
27</div>\r
28<div id="content">\r
29<div id="preamble">\r
30<div class="sectionbody">\r
31<div class="paragraph"><p>MLton runs fine on <a href="http://www.freebsd.org/">FreeBSD</a>.</p></div>\r
32</div>\r
33</div>\r
34<div class="sect1">\r
35<h2 id="_notes">Notes</h2>\r
36<div class="sectionbody">\r
37<div class="ulist"><ul>\r
38<li>\r
39<p>\r
40MLton is available as a <a href="http://www.freebsd.org/">FreeBSD</a>\r
41<a href="http://www.freebsd.org/cgi/ports.cgi?query=mlton&amp;stype=all">port</a>.\r
42</p>\r
43</li>\r
44</ul></div>\r
45</div>\r
46</div>\r
47<div class="sect1">\r
48<h2 id="_known_issues">Known issues</h2>\r
49<div class="sectionbody">\r
50<div class="ulist"><ul>\r
51<li>\r
52<p>\r
53Executables often run more slowly than on a comparable Linux\r
54machine. We conjecture that part of this is due to costs due to heap\r
55resizing and kernel zeroing of pages. Any help in solving the problem\r
56would be appreciated.\r
57</p>\r
58</li>\r
59<li>\r
60<p>\r
61FreeBSD defaults to a datasize limit of 512M, even if you have more\r
62than that amount of memory in the computer. Hence, your MLton process\r
63will be limited in the amount of memory it has. To fix this problem,\r
64turn up the datasize and the default datasize available to a process:\r
65Edit <span class="monospaced">/boot/loader.conf</span> to set the limits. For example, the setting\r
66</p>\r
67<div class="listingblock">\r
68<div class="content monospaced">\r
69<pre> kern.maxdsiz="671088640"\r
70 kern.dfldsiz="671088640"\r
71 kern.maxssiz="134217728"</pre>\r
72</div></div>\r
73<div class="paragraph"><p>will give a process 640M of datasize memory, default to 640M available\r
74and set 128M of stack size memory.</p></div>\r
75</li>\r
76</ul></div>\r
77</div>\r
78</div>\r
79</div>\r
80<div id="footnotes"><hr></div>\r
81<div id="footer">\r
82<div id="footer-text">\r
83</div>\r
84<div id="footer-badges">\r
85</div>\r
86</div>\r
87</body>\r
88</html>\r