• Home
  • History
  • Annotate
  • only in this directory
NameDateSize

..02-May-201770

bench_001.cH A D19-Dec-20119 KiB

csv/H02-May-201716

ex_access.cH A D19-Dec-20113.5 KiB

ex_apprec/H02-May-201711

ex_btrec.cH A D19-Dec-20114.6 KiB

ex_dbclient.cH A D19-Dec-20114.9 KiB

ex_env.cH A D19-Dec-20113.1 KiB

ex_lock.cH A D19-Dec-20115.2 KiB

ex_mpool.cH A D19-Dec-20115.5 KiB

ex_rep/H02-May-20176

ex_sequence.cH A D19-Dec-20112.7 KiB

ex_thread.cH A D19-Dec-201112.8 KiB

ex_tpcb.cH A D19-Dec-201117.5 KiB

getting_started/H02-May-20178

READMEH A D19-Dec-20111.3 KiB

tagsH A D07-Apr-2013392.4 KiB

txn_guide/H02-May-20174

README

1# $Id: README,v 12.1 2006/07/07 23:36:14 alanb Exp $
2
3getting_started/
4		Examples from the Getting Started Guide
5
6bench_001.c	Micro-benchmark for the bulk fetch interface.
7
8ex_access.c	Using just the DB access methods.
9
10ex_apprec/	Application-specific recovery.
11
12ex_btrec.c	Using the BTREE access method with record numbers.
13
14ex_dbclient.c	Using DB from an RPC client.
15
16ex_env.c	Setting up the DB environment.
17
18ex_lock.c	Locking.
19
20ex_mpool.c	Shared memory buffer pools.
21
22ex_rep/		Replication.  This creates a toy stock quote server
23		with DB's single-master, multiple-client replication,
24		with communication over TCP.  See ex_rep/README.
25
26ex_sequence.c	Sequences.
27
28ex_thread.c	Threaded application with multiple readers and writers.
29
30ex_tpcb.c	TPC/B.
31		Ex_tpcb sets up a framework in which to run a TPC/B test.
32		Database initialization (the -i flag) and running the
33		benchmark (-n flag) must take place separately (i.e.,
34		first create the database, then run 1 or more copies of
35		the benchmark).  Furthermore, when running more than one
36		TPCB process, it is necessary to run the deadlock detector
37		(db_deadlock), since it is possible for concurrent tpcb
38		processes to deadlock.  For performance measurement, it
39		will also be beneficial to run the db_checkpoint process
40		as well.
41