-
-
Notifications
You must be signed in to change notification settings - Fork 130
/
NOTICE
179 lines (125 loc) · 6.61 KB
/
NOTICE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
[The Hoard Memory Allocator](http://www.hoard.org)
--------------------------
[](https://travis-ci.org/emeryberger/Hoard)
Copyright (C) 1998-2019 by [Emery Berger](http://www.emeryberger.org)
The Hoard memory allocator is a fast, scalable, and memory-efficient
memory allocator that works on a range of platforms, including Linux,
Mac OS X, and Windows.
Hoard is a drop-in replacement for malloc that can dramatically
improve application performance, especially for multithreaded programs
running on multiprocessors and multicore CPUs. No source code changes
necessary: just link it in or set one environment variable (see
[Building Hoard](#building-hoard-unixmac), below).
Press
-----
* "If you'll be running on multiprocessor machines, ... use Emery
Berger's excellent Hoard multiprocessor memory management code. It's a
drop-in replacement for the C and C++ memory routines and is very fast
on multiprocessor machines."
* [Debugging Applications for Microsoft .NET and Microsoft Windows, Microsoft Press](http://www.microsoft.com/mspress/books/5822.aspx)
* "(To improve scalability), consider an open source alternative such as
the Hoard Memory Manager..."
* [Windows System Programming, Addison-Wesley](http://www.amazon.com/Windows-Programming-Addison-Wesley-Microsoft-Technology/dp/0321657748/)
* "Hoard dramatically improves program performance through its more
efficient use of memory. Moreover, Hoard has provably bounded memory
blowup and low synchronization costs."
* [Principles of Parallel Programming, Addison-Wesley](http://www.amazon.com/Principles-Parallel-Programming-Calvin-Lin/dp/0321487907/)
Users
-----
Companies using Hoard in their products and servers include AOL,
British Telecom, Blue Vector, Business Objects (formerly Crystal
Decisions), Cisco, Credit Suisse, Entrust, InfoVista, Kamakura,
Novell, Oktal SE, OpenText, OpenWave Systems (for their Typhoon and
Twister servers), Pervasive Software, Plath GmbH, Quest Software,
Reuters, Royal Bank of Canada, SAP, Sonus Networks, Tata
Communications, and Verite Group.
Open source projects using Hoard include the Asterisk Open Source
Telephony Project, Bayonne GNU telephony server, the Cilk parallel
programming language, the GNU Common C++ system, the OpenFOAM
computational fluid dynamics toolkit, and the SafeSquid web proxy.
Hoard is now a standard compiler option for the Standard Performance
Evaluation Corporation's CPU2006 benchmark suite for the Intel and
Open64 compilers.
Licensing
---------
Hoard is distributed under the GPL (v2.0), and can also be licensed
for commercial use.
Because of the restrictions imposed by the GPL license (you must make
your code open-source), commercial users of Hoard can purchase non-GPL
licenses through the University of Texas at Austin. Please consult the
[current Hoard pricing
information](http://www.cs.umass.edu/~emery/hoard/Hoard%20Pricing%202-05-2009.pdf)
(updated 2/5/2009), which lists a number of options for purchasing
licenses, as well as [software license terms and
conditions](http://www.cs.umass.edu/~emery/hoard/SLA%20Terms%20and%20Conditions%209.22.2006.pdf),
and the [software license
agreement](http://www.cs.umass.edu/~emery/hoard/SLA%20Short%20Form%209-26-2006.pdf):
note that the [main UT-Austin licensing
page](http://www.otc.utexas.edu/IndustryForms.jsp) always contains the
most up-to-date documents.
To obtain a license, please contact Jitendra Jain directly
(jjain@otc.utexas.edu) and copy Emery Berger (emery@cs.umass.edu).
Jitendra Jain's full contact information follows:
Jitendra Jain
The University of Texas at Austin
Office of Technology Commercialization
MCC Building, Suite 1.9A
3925 West Braker Lane
Austin, Texas 78759
(512) 471-9055, (512) 475-6894 (fax)
Why Hoard?
----------
There are a number of problems with existing memory allocators that
make Hoard a better choice.
### Contention ###
Multithreaded programs often do not scale because the heap is a
bottleneck. When multiple threads simultaneously allocate or
deallocate memory from the allocator, the allocator will serialize
them. Programs making intensive use of the allocator actually slow
down as the number of processors increases. Your program may be
allocation-intensive without you realizing it, for instance, if your
program makes many calls to the C++ Standard Template Library (STL). Hoard eliminates this bottleneck.
### False Sharing ###
System-provided memory allocators can cause insidious problems for multithreaded code. They can
lead to a phenomenon known as "false sharing": threads on different CPUs
can end up with memory in the same cache line, or chunk of
memory. Accessing these falsely-shared cache lines is hundreds of
times slower than accessing unshared cache lines. Hoard is designed to prevent false sharing.
### Blowup ###
Multithreaded programs can also lead the allocator to blowup memory
consumption. This effect can multiply the amount of memory needed to
run your application by the number of CPUs on your machine: four CPUs
could mean that you need four times as much memory. Hoard is guaranteed (provably!) to bound memory consumption.
Building Hoard (Unix/Mac)
-------------------------
To build Hoard on non-Windows platforms, change into the `src/`
directory and run `make` (or `gmake`) followed by the appropriate
target. It should automatically detect your system and build
appropriately.
% make
You can then use Hoard by linking it with your executable, or
by setting the `LD_PRELOAD` environment variable, as in
% export LD_PRELOAD=/path/to/libhoard.so
or, in Mac OS X:
% export DYLD_INSERT_LIBRARIES=/path/to/libhoard.dylib
Building Hoard (Windows)
------------------------
Change into the `src` directory and build the Windows version:
C:\hoard\src> nmake
To use Hoard, link your executable with `source\uselibhoard.cpp` and `libhoard.lib`.
You *must* use the `/MD` flag.
Example:
C:\hoard\src> cl /Ox /MD yourapp.cpp source\uselibhoard.cpp libhoard.lib
To run `yourapp.exe`, you will need to have `libhoard.dll` in your path.
Benchmarks
----------
The directory `benchmarks/` contains a number of benchmarks used to
evaluate and tune Hoard.
Technical Information
---------------------
Hoard has changed quite a bit over the years, but for technical details of the first version of Hoard, read [Hoard: A
Scalable Memory Allocator for Multithreaded Applications](http://dl.acm.org/citation.cfm?id=379232),
by Emery D. Berger, Kathryn S. McKinley, Robert D. Blumofe, and Paul
R. Wilson. The Ninth International Conference on Architectural Support
for Programming Languages and Operating Systems
(ASPLOS-IX). Cambridge, MA, November 2000.