[elephant-cvs] CVS elephant

[ieslick]

Update of /project/elephant/cvsroot/elephant
In directory clnet:/tmp/cvs-serv4997

Modified Files:
	TODO config.sexp 
Log Message:
Export bdb performance tweaks; lots more documentation; new ops for libberkeley-db

--- /project/elephant/cvsroot/elephant/TODO	2007/04/19 22:25:50	1.80
+++ /project/elephant/cvsroot/elephant/TODO	2007/04/25 02:27:56	1.81
@@ -28,7 +28,6 @@
   - More notes about transaction performance
   - Serious discussion of threading implications
   - Add notes about with/ensure-transaction usage (abort & commit behavior on exit)
-  - Add notes about optimize-storage
   - Add notes about deadlock-detect
   - Add notes about checkpoint (null in SQL?)
 
--- /project/elephant/cvsroot/elephant/config.sexp	2007/04/19 05:51:33	1.10
+++ /project/elephant/cvsroot/elephant/config.sexp	2007/04/25 02:27:56	1.11
@@ -4,6 +4,7 @@
  (:berkeley-db-lib . "/opt/local/lib/db45/libdb-4.5.dylib")
  (:berkeley-db-deadlock . "/opt/local/bin/db45_deadlock")
  (:pthread-lib . nil)
+ (:berkeley-db-cachesize . 20971520)
  (:clsql-lib . nil)
  (:compiler . :gcc))
 
@@ -46,4 +47,21 @@
 ;; :compiler options are 
 ;;           :gcc (default: for unix platforms with /usr/bin/gcc)
 ;;           :cygwin (for windows platforms with cygwin/gcc)
-;;           :msvc (unsupported)
\ No newline at end of file
+;;           :msvc (unsupported)
+;;
+;; Additional supported parameters include:
+;;
+;;
+;; :berkeley-db-cachesize - an integer indicating the number of bytes
+;;                          for the page cache, default 10MB which is
+;;                          about enough storage for 10k-30k indexed
+;;                          persistent objects
+;;
+;; :map-using-degree2 - Boolean parameter that indicates whether map
+;;                      operations lock down the btree for the entire
+;;                      transaction or whether they allow other
+;;                      transactions to add/delete/modify values
+;;                      before the map operation is completed.  The
+;;                      map operation remains stable and any writes
+;;                      are kept transactional, see user manual as
+;;                      well as berkeley DB docs for more details