Thanks for trying it, and sorry your initial trial did not work out. We hope to improve the experience as the product gains some mileage.
If you are using Ubuntu then the way to disable the module entirely is to remove pagespeed.load and pagespeed.conf from the /etc/apache2/mods-enabled directory.
If you are using CentOS then the you would remove /etc/httpd/conf.d/pagespeed.conf
This should help httpd 'forget' that mod_pagespeed ever existed.
You can also try controlling the resource usage with the pagespeed.conf directives:
ModPagespeedFileCacheSizeKb
ModPagespeedLRUCacheKbPerProcess
The numbers that we have put into the default configuration for these directives have not been well-tuned for production systems.
How much disk space is mod_pagespeed consuming? Is it exceeding the threshold set in the configuration file? It's possible that your disk space is growing faster than our periodic cleanup task that deletes old files, which is controlled by the directive
ModPagespeedFileCacheCleanIntervalMs
If you are concerned about memory usage on your server, please try setting ModPagespeedLRUCacheKbPerProcess to 0. The per-process LRU cache is intended to accelerate cache-lookups on high QPS server but it is possible to run without the per-process memory-based cache.
Thanks everyone for your patience as we gain knowledge of how to tune this product for live traffic.
-Josh