Disable most debugging print messages; should help with performance.

[bluesky.git] / bluesky / init.c

diff --git a/bluesky/init.c b/bluesky/init.c
index 9fb9332..fee9aad 100644 (file)
--- a/bluesky/init.c
+++ b/bluesky/init.c
@@ -13,8 +13,31 @@
 
 #include "bluesky-private.h"
 
+int bluesky_verbose = 0;
+
 BlueSkyOptions bluesky_options;
 
+/* Maximum number of threads to use in any particular thread pool, or -1 for no
+ * limit */
+int bluesky_max_threads = 16;
+
+/* Watermark levels for cache tuning: these control when dirty data is flushed
+ * from cache, when clean data is dropped from the cache, etc.  These values
+ * are measured in blocks, not bytes.
+ *
+ * There are a few relevant levels:
+ *   low: Below this point, data is not forced out due to memory pressure
+ *   medium: At this point start flushing data to get back below medium
+ *   high: Flush data very aggressively (launch extra tasks if needed)
+ */
+int bluesky_watermark_low_dirty    = (64 << 20) / BLUESKY_BLOCK_SIZE;
+int bluesky_watermark_medium_dirty = (96 << 20) / BLUESKY_BLOCK_SIZE;
+int bluesky_watermark_high_dirty   = (192 << 20) / BLUESKY_BLOCK_SIZE;
+
+int bluesky_watermark_low_total    = (64 << 20) / BLUESKY_BLOCK_SIZE;
+int bluesky_watermark_medium_total = (128 << 20) / BLUESKY_BLOCK_SIZE;
+int bluesky_watermark_high_total   = (256 << 20) / BLUESKY_BLOCK_SIZE;
+
 /* Environment variables that can be used to initialize settings. */
 static struct {
     const char *env;