blitz_stable: config/blitz-act.config comparison

comparison config/blitz-act.config @ 0:3dc0c5604566

Initial checkin of blitz 2.0 fcs - no installer yet.

author	Dan Creswell <dan.creswell@gmail.com>
date	Sat, 21 Mar 2009 11:00:06 +0000
parents
children

comparison

equal deleted inserted replaced

--1:000000000000
+:3dc0c5604566
+import net.jini.discovery.DiscoveryGroupManagement;
+import java.rmi.activation.ActivationID;
+import java.util.logging.Level;
+import net.jini.security.BasicProxyPreparer;
+import net.jini.core.discovery.LookupLocator;
+import net.jini.jeri.tcp.TcpServerEndpoint;
+import net.jini.jeri.ProxyTrustILFactory;
+import net.jini.jeri.BasicILFactory;
+import net.jini.jeri.BasicJeriExporter;
+import net.jini.jrmp.JrmpExporter;
+import net.jini.activation.ActivationExporter;
+import org.dancres.blitz.stats.Switch;
+import org.dancres.blitz.stats.OpSwitch;
+import org.dancres.blitz.stats.InstanceSwitch;
+import org.dancres.blitz.remote.debug.DebugILFactory;
+import org.dancres.blitz.lease.LeaseReaper;
+import org.dancres.blitz.config.Persistent;
+import org.dancres.blitz.config.TimeBarrierPersistent;
+import org.dancres.blitz.config.Transient;
+import org.dancres.blitz.config.EntryConstraint;
+import org.dancres.blitz.config.CacheSize;
+import org.dancres.blitz.config.Fifo;
+import net.jini.core.entry.Entry;
+org.dancres.blitz {
+// logDebug = new Boolean(true);
+// disableBitmaps = new Boolean(true);
+// Default logging level
+//
+defaultLogLevel = Level.SEVERE;
+// ignoreLogConfig = new Boolean(true);
+// Examples of setting log levels for specific components
+//
+// org_dancres_blitz_disk_DiskLogLevel = Level.INFO;
+// org_dancres_blitz_entry_SearchVisitorImplLogLevel = Level.FINE;
+// org_dancres_blitz_arc_cacheLogLevel = Level.INFO;
+// org_dancres_blitz_oid_AllocatorLogLevel = Level.ALL;
+// org_dancres_blitz_txn_LogBatcherLogLevel = Level.ALL;
+// Published on the proxy as a Name attribute
+//
+name = "dancres";
+// Set this to a LoginContext instance when you wish to run the server
+// as a particular principle
+//
+// loginContext =
+// Location to store meta info and entrys.
+// NOTE: Each concurrent Blitz instance should use a different directory
+// for it's logs and persistent state - if this isn't done
+// "bad things will happen" (TM)
+//
+persistDir = "/Users/dan/src/jini/blitz_pj/dbfiles_dancres";
+// Location of log files - SHOULD BE DIFFERENT FROM ABOVE
+//
+logDir = "/Volumes/log/dan/prevlog/";
+// Maximum number of async write threads
+// DO NOT CHANGE THIS - BLITZ DOESN'T SUPPORT MORE THAN ONE WRITE THREAD
+// (YET!)
+//
+maxWriteThreads = 1;
+// How long to keep write threads alive in the pool
+//
+threadKeepalive = 15;
+// The preferred queue size for pending writes
+//
+desiredPendingWrites = 4000;
+// throttlePendingWrites = 8000;
+throttlePendingWrites = Integer.MAX_VALUE;
+// Size of the berkeley DB cache
+//
+// dbCache = 8388608;
+dbCache = 33554432;
+// dbCache = 268435456;
+// dbCache = 134217728;
+// dbCache = 536870912;
+// Configures the maximum number of concurrent Db transactions
+// Bigger is better!  This value has been validated for 64 concurrent
+// JavaSpace operations
+//
+maxDbTxns = 256;
+// Dump Db statistics after every checkpoint if this is true
+// WARNING: dumping stats is broken in 4.1.25 -
+// ask Dan (dan@dancres.org) for a patch.  This should be fixed in Db 4.2,
+// will test and then post an update to the website
+//
+dumpDbStats = new Boolean(false);
+// Dump statistics for write queue usage
+// When tuning/configuring Blitz for various systems, these stats help
+// to determine I/O performance requirements and required memory
+//
+dumpWQStats = new Boolean(false);
+// Turn this on to get reports on checkpointing behaviour - useful for
+// tuning
+logCkpts = new Boolean(true);
+// Maximum number of entry instances to cache for a particular Entry type
+//
+// entryReposCacheSize = 512;
+//entryReposCacheSize = 1024;
+entryReposCacheSize = 4096;
+// entryReposCacheSize = 8192;
+// entryReposCacheSize = 100;
+// maxDbLog = 50000000;
+// Type specific constraints - define a variable using the classname of
+// the type, replaceing . or $ with _.  The variable should then be
+// initialized to an array of EntryConstraints specifying requirements.
+// Note, if you wish to enable FIFO, reduce pendingWrites queue
+//
+// org_dancres_blitz_SpaceWriteTakeTest_TestEntry =
+//   new EntryConstraint[] {new CacheSize(512), new Fifo()};
+// org_dancres_blitz_SpaceFifonessTest_TestEntry =
+//   new EntryConstraint[] {new CacheSize(1024), new Fifo()};
+// org_dancres_blitz_test_DummyEntry =
+	//     new EntryConstraint[] {new CacheSize(1024), new Fifo()};
+// org_dancres_blitz_SpaceFifonessTest_TestEntry =
+	//     new EntryConstraint[] {new CacheSize(512)};
+// Non-blocking transactions are used within the entry package to
+// prevent deadlock.  Such transactions can fail and require aborting
+// should they fail to get a lock.  When this happens, the thread
+// attempting the transaction will backoff by an amount of time dictated
+// by base_backoff + Random(jitter) ms which should allow the conflicting
+// transaction time to complete.  Format is {base_backoff, jitter}
+loadBackoff = new int[] {20, 50};
+// The maximum allowable lease time for entries and notify registrations
+// To permit Lease.FOREVER, set the LeaseBound = 0.
+// To deny Lease.FOREVER and set an upper limit on lease time set the
+// LeaseBound to a positive non-zero value in milliseconds
+//
+entryLeaseBound = 0;
+notifyLeaseBound = 0;
+//    eventQueueBound = 20;
+//    taskQueueBound = 100;
+// How often to do an active cleanup of lease expired resources
+// Value should be ms - 0 disables active cleanup.  Normally, Blitz
+// uses read/take activity to do cleanup (passive).  If memory or
+// disk resource is scarce, configure this to non-zero to activate more
+// aggressive cleaning (which, in turn, is more CPU aggressive).
+//
+leaseReapInterval = 0;
+// leaseReapInterval = LeaseReaper.MANUAL_REAP;
+// leaseReapInterval = 1800000;
+// Number of OID allocators to use for entries
+maxOidAllocators = 512;
+// How often to log event allocation to disk
+//
+eventgenSaveInterval = 50;
+// How big a jump in notify sequence numbers there should be following
+// restart/crash
+//
+eventgenRestartJump = 1000;
+// Maximum number of task threads to be used in posting remote events
+// and dispatching blocked takes or reads
+//
+maxTaskThreads = 10;
+storageModel = new Transient();
+// storageModel = new TimeBarrierPersistent(true, true, 50000, 262144, 5000);
+// Persistent storage settings
+// Note:  The third parameter (batching time) can radically affect
+// throughput in concurrent conditions.  You're advised to try various
+// settings for your desired load as variations in OS and hard-disk
+// performance determine what is appropriate for each machine.
+//
+// Note:  The final parameter (buffer size) can also radically affect
+// throughput.  It needs to be large enough to hold all transactional
+// information produced by the batcher.  Thus if your average load is
+// 20 transactions, you will want to scale the buffer size to hold 20
+// transactions worth of operations.
+//
+// For raw, single-threaded benchmarks, use 0 log buffering time
+// storageModel = new Persistent(true, true, 0, true, 100, 8192);
+// For concurrent benchmark or application use non-zero log buffering time
+// storageModel = new Persistent(true, true, 10, true, 10000, 32768);
+// Use this setting for network usage - we add additional time to
+// log-buffering to account for network latency
+//
+// storageModel = new Persistent(true, true, 20, true, false, 20000, 8192);
+debugPort = 0;
+// debugPort = 12345;
+// Enable standard destroy semantics - by default, Blitz does NOT
+// delete state at destroy.  Enable that feature here and invoke
+// BlitzAdmin::shutdown to perform a shutdown whilst retaining state
+compliantDestroy = new Boolean(false);
+// Default Stats to make available
+stats = new Switch[] {new OpSwitch(OpSwitch.ALL_TYPES,
+		OpSwitch.TAKE_OPS, true),
+		new OpSwitch(OpSwitch.ALL_TYPES, OpSwitch.READ_OPS, true),
+		new OpSwitch(OpSwitch.ALL_TYPES, OpSwitch.WRITE_OPS, true),
+		new InstanceSwitch(InstanceSwitch.ALL_TYPES, true)};
+// The initial lookup groups to register with - after first boot
+// this information is held in a meta database and should be configured
+// via JoinAdmin
+//
+// initialGroups = new String[]{};
+// initialGroups = new String[]{"JERI_Group1"};
+// initialGroups = DiscoveryGroupManagement.ALL_GROUPS;
+// The initial lookup locators to register with - after first boot
+// this information is held in a meta database and should be configured
+// via JoinAdmin
+//
+// initialLocators = new LookupLocator[] {new LookupLocator("jini://rogue/")};
+// The initial attributes to register with - note that these need to be
+// available as part of the codebase.
+// This information is held in a meta database and should be configured
+// via JoinAdmin
+//
+// initialAttrs = new Entry[] {};
+// The exporter to use - see the JINI documentation
+//
+// serverExporter = new JrmpExporter();
+// For ACTIVATION, we must nest a normal exporter inside an activation
+// exporter instance.
+//
+exporter= new BasicJeriExporter(TcpServerEndpoint.getInstance(0),
+new ProxyTrustILFactory(null, null), false, true);
+//use an ActivationExporter to create a persistent ref
+serverExporter= new ActivationExporter((ActivationID) $data,exporter);
+// Blitz provides a suitable default for all these but this is how you'd
+// configure them explicitly
+//
+notifyPreparer = new BasicProxyPreparer();
+recoveredNotifyPreparer = new BasicProxyPreparer();
+txnPreparer = new BasicProxyPreparer();
+recoveredTxnPreparer = new BasicProxyPreparer();
+activationIdPreparer = new BasicProxyPreparer();
+activationSysPreparer = new BasicProxyPreparer();
+}

Mercurial > hg > blitz_stable

comparison config/blitz-act.config @ 0:3dc0c5604566