[GitHub] [trafficserver] rob05c commented on issue #8713: ZFS Integration

[GitBox <gi...@apache.org>]

rob05c commented on issue #8713:
URL: https://github.com/apache/trafficserver/issues/8713#issuecomment-1063379521


   Do you mean for ATS itself? Or for its cache?
   
   I'm not aware of anyone having tested, but I can hypothesize.
   
   For ATS itself, it shouldn't affect performance. ATS doesn't request things from disk during HTTP requests, other than the cache. ZFS might make it a little slower to load and reload config files. But it shouldn't affect requests/second.
   
   ATS is capable of using both raw block devices or ordinary files as a disk cache.
   
   If you mean using a file on a ZFS filesystem as a disk cache -- I wouldn't recommend it.
   
   Giving ATS a raw block device for a cache is highly recommended for production systems. Raw block devices perform significantly better than files on filesystems, due to the overhead of the filesystem. A next-generation FS like ZFS will likely perform worse than a previous gen like ext4, because of overhead like checksums. On the other hand, ZFS has memory caching, so it might actually perform better.
   
   But raw block devices are highly recommended. ATS has its own memory cache in front of the disk cache, and the disk cache is optimized for block devices, and it avoids all that unnecessary filesystem overhead.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org