11 Commits

Author	SHA1	Message	Date
Wilfried Goesgens	1ae5f8daec	split headers different, simple cast fixes (#8928)	2019-05-08 14:08:35 +02:00
Jan	3320052f5d	do not include our datafiles in core files (#2630)	2017-06-22 12:34:27 +02:00
Frank Celler	d6e8046992	updated cleanupCFiles	2016-04-23 16:34:57 -07:00
Jan Steemann	9046e1831b	clang-format	2016-01-27 13:43:46 +01:00
Jan Steemann	3ad20c0cae	auto-generated headers	2016-01-06 18:41:51 +01:00
Jan Steemann	a3b026d9d1	removed useless sections from code, unified include guards	2016-01-06 14:15:22 +01:00
Jan Steemann	f422576ee0	clang-format	2016-01-05 17:43:24 +01:00
Max Neunhoeffer	c0f1b72bab	Add "sensible" madvise calls. ... Essentially the strategy is: A newly created and a newly opened file is advised to be "SEQUENTIAL ACCESS", because we will either write to it or scan it sequentially. As soon as it is sealed, we switch the advice to "RANDOM ACCESS", because this should be the normal pattern and aggressive read-aheads tend to be bad. The collector and the compactor switch a sealed file back to "SEQUENTIAL ACCESS" just before they scan it and back to "RANDOM ACCESS", when they are done. Furthermore, all data files in a collection are advised with "WILLNEED" just before the collection is scanned during loading. Finally, the actual hash table of AssocMulti is advised to be random access, although this is an anonymous map given to us by malloc and not a memory mapped file.	2015-08-26 16:45:26 +02:00
Jan Steemann	4e6f6f2cbd	finalized move to cxx	2014-09-14 00:06:00 +02:00
Jan Steemann	aa20c9e980	renamed last C files...	2014-09-13 22:38:25 +02:00
Jan Steemann	506936dcdb	rename orgy	2014-09-13 02:35:13 +02:00