Skip to content

Releases: GoogleCloudPlatform/gcsfuse

Gcsfuse v2.0.0

15 Mar 06:57
3349a76
Compare
Choose a tag to compare
  1. File caching: A client-based local file cache that lets repeat file reads be served from a faster cache storage of your choice, such as a Local SSD, Persistent Disk, or in-memory /tmpfs. It significantly improves your read performance on subsequent reads/epochs. (more details here)

    • New config-file flags (more details here)
          cache-dir: (default=””)
          file-cache:
              max-size-mb: (default=-1) 
              cache-file-for-range-read: (default=false)
      
    • Behavior:
      • cache-dir: The file-cache feature is disabled by default. To enable it, pass a directory to cache-dir.
      • max-size-mb: This is used to limit the total capacity that the Cloud Storage FUSE cache can use within the specified cache directory. The eviction of cached data is based on a least recently used (LRU) algorithm. By default, a value of -1 signifies all available capacity in the specified directory.
      • cache-file-for-range-read: Enable file cache for Random & partial reads: Support for asynchronous cache ingestion of files on offset reads through cache-file-for-range-read.
  2. Updates to metadata-cache (stat & type caches) feature
    More details here.

    • Deprecated CLI flags
      • stat-cache-capacity was replaced with metadata-cache:stat-cache-max-size-mb.
      • stat-cache-ttl & type-cache-ttl were replaced with metadata-cache:ttl-secs.
    • New config-file flags (more details here)
         metadata-cache: 
               stat-cache-max-size-mb: (default=32)
               ttl-secs: (default=60)
               type-cache-max-size-mb: (default=4)
      
    • Behavior changes
      • type-cache-max-size-mb: Type-cache size limit can now be configured using this configuration, at per-directory level.
      • stat-cache-max-size-mb: The stat-cache size limit is now configured as memory size (in MiB) using this configuration instead of capacity (count of entries). Also, stat-cache is now configured at mount-level as opposed to bucket-level.
      • ttl-secs: stat-cache and type-cache TTLs have been merged into a single-TTL value, configurable via this configuration. Also, this new TTL is set as an integer multiple of seconds, as opposed to fine-grained duration (such as 1s500ms with the old flags).
      • To get the best performance, stat-cache-max-size-mb, ttl-secs and type-cache-max-size-mb can be individually set to -1 for unlimited size/ttl limits. Setting any of them to 0 disables the corresponding cache.
      • Use of deprecated flags will give warning, but for backward compatibility, their values will still heuristically be converted to the new flags and will be used. If both new and old flags are set, old flags are ignored.
  3. Managed folders compatibility

    • GCSFuse respects the managed folder IAM permissions in the bucket mounted with GCSFuse.
    • Pass --implicit-dir flag to view managed folders.
  4. Memory Improvements

    • The average memory usage of stat-cache is now reduced by up to 40%.
  5. Bug fixes and improvements

    • Fix concurrent list directory and file creation
    • Improvements in logging
      • Added log for successful/failed mounting on stdout when log-file is set in non-foreground mode.
  6. Removed --experimental-local-file-cache flag which used to be for an old experimental local file cache feature.

  7. Upgraded dependencies for better stability and reliability. (#1744, #1746)

Gcsfuse v2.0.0~beta.1

16 Feb 17:06
b700e15
Compare
Choose a tag to compare
Gcsfuse v2.0.0~beta.1 Pre-release
Pre-release
v2.0.0_beta.1

Enable or disable file cache via cache-dir (#1723)

Gcsfuse v1.4.2

26 Feb 15:30
342c39b
Compare
Choose a tag to compare
  • Upgrade Go to v1.21.6 (from v1.21.5)
  • [Perf Improvement] Improved read performance by reusing existing readers for subsequent reads. This reduced the overhead of unnecessary GCS connections and increased end-to-end read-bandwidth up to 75% for files smaller than 1 MB. (#1683)
  • Bump dependencies (#1630, #1650, #1671, #1672)

What's Changed

Full Changelog: v1.4.1...v1.4.2

Early Beta Release for GCS Fuse v2.0.0

08 Feb 09:42
Compare
Choose a tag to compare
Pre-release

Early Beta Release for GCS Fuse v2.0.0

Gcsfuse v1.4.1

22 Jan 10:45
56230ed
Compare
Choose a tag to compare
  • GCSFuse JSON format logs now seamlessly integrate with google-fluentd, enabling easier log analysis and management within Google Cloud's logging ecosystem. (Reference: http://cloud.google.com/logging/docs/agent/logging/configuration)
  • #1541 GCSFuse now adheres to proxy settings defined in environment variables (HTTP_PROXY, HTTPS_PROXY), providing greater adaptability in various network configurations.
  • GCSFuse mount command is now logged at INFO level, providing better visibility into mount operations and aiding in troubleshooting.

What's Changed

Full Changelog: v1.4.0...v1.4.1

Gcsfuse v1.4.0

27 Dec 08:25
90a4927
Compare
Choose a tag to compare
  • Added support for PyTorch 2.0
  • Upgraded the following dependency packages for fixing the given CVEs

What's Changed

Full Changelog: v1.3.0...v1.4.0

Gcsfuse v1.3.0

07 Dec 11:25
de3b3bc
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.2.1...v1.3.0

Gcsfuse v1.2.1

08 Nov 10:09
70ed0ef
Compare
Choose a tag to compare

Gcsfuse v1.2.0

26 Sep 01:25
eb75e8f
Compare
Choose a tag to compare
  • Improved performance by removing zero-byte file creation during write flow (details here).
  • GCSFuse is now available for use on arm64-based machines.
  • Improved logging - by supporting different log-levels (documentation here).
  • Improved coverage by adding more e2e/integration tests.
  • Added new flag --config-file which supports specifying new flags via yaml file (documentation here).
  • Upgraded go version from 1.20.5 to 1.21.0.

Gcsfuse v1.1.0

28 Aug 20:24
19ed094
Compare
Choose a tag to compare
  • Reading compressed objects (gzip) in compressed format is now supported.
  • Deprecated --enable-storage-client-library flag. With this deprecation, GCSfuse will always use the Go Storage client to interact with GCS. Please reach out to us on Discussions or Issues section in case you face any issues with the deprecation.
  • Changed name of --endpoint flag to --custom-endpoint. Note: When --custom-endpoint is specified, authentication with the endpoint is disabled.
  • Upgraded versions of couple of dependencies i.e. Go Storage client version from 1.29.0 to 1.31.0 & jacobsa/fuse.
  • Shifted from custom implementation of rate limiter to Go’s rate limiter. No changes in the functionality.
  • Added more e2e/integration tests.
  • Minor bug fixes in tests & build packages.