Stasis is a flexible transactional storage library for high-performance applications and system developers. It supports concurrent transactional storage and no-FORCE/STEAL buffer management.
44a766a7f6
set clean and unpinned while the slow handle was writing them back. This allowed other threads to come in, and read the old version of the page from disk. * Fixed performance bug: When considering pages for writeback, start after the end of the last flushed page (not the first flushed page) * Honor "max_fast_handles". |
||
|---|---|---|
| benchmarks | ||
| blast | ||
| doc | ||
| examples | ||
| libdfa | ||
| m4 | ||
| pbl | ||
| pobj | ||
| src | ||
| stasis | ||
| test | ||
| utilities | ||
| .cvsignore | ||
| AUTHORS | ||
| bootstrap | ||
| ChangeLog | ||
| clean.sh | ||
| configure.in | ||
| COPYING | ||
| cvs-branch-info | ||
| lladd.prj | ||
| lladd.pws | ||
| Makefile.am | ||
| mkinstalldirs | ||
| NEWS | ||
| NOTES | ||
| README | ||
| reconf | ||
| reconf-1.8 | ||
| stamp-h.in | ||
Stasis is an experimental flexible transactional storage library. Please see the COPYING file for licensing information. More information about installation, a tutorial and API documentation are available at: http://lladd.sourceforge.net/developers/html/ First, make sure you have the appropriate dependencies: 'make check' requires the GNU check library, 'make doc' requires Doxygen. You'll need Berkeley DB to build; it isn't actually used by Stasis, but I haven't gotten around to making it optional. You also need libconfuse; it is used by some of the programs that ship with Stasis. To build, do: ./reconf or ./reconf-1.8 You'll need to have a version of automake >= 1.7 for ./reconf to work, or have automake 1.8 for ./reconf-1.8 to work. Different packages of automake should be able to coexist on the same system, and probably ship with your distribution. ./configure make make check make install To build the API and internals documentation, run: make docs after configure. We don't support "make install". ;) For up-to date coverage reports and unit test pass rates, see http://www.cs.berkeley.edu/~sears/stasis/ The unit test logs for lcov describe how the coverage report was generated.