I stumbled upon a blogpost where Jorg Hoh claims that putting your TarMK on an NFS is not a good idea because mmap (Java 1.7) won't work with that configuration.
Short summary: Having TarMK storage on an NFS causes a huge performance impact as AEM won't be able to take advantage of memory mapped files.
Is there anyone who can confirm or deny this?
With me this also raises the question on how this will work with a SAN, I assume having a SAN mounted disk won't have the same issues as an NFS.
Link to the original post:https://cqdump.wordpress.com/2016/02/23/tarmk-on-nas/
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
When you have a SAN, you normally have a local filesystem (NTFS, ext4, btrfs, ...) on top of the SAN volume. Then you don't have this performance impact. My experiences with SAN and TarMK are quite good.
See also https://cqdump.wordpress.com/2016/02/24/tarmk-and-san/
Kind regards,
Jörg
Views
Replies
Total Likes
Hi,
When you have a SAN, you normally have a local filesystem (NTFS, ext4, btrfs, ...) on top of the SAN volume. Then you don't have this performance impact. My experiences with SAN and TarMK are quite good.
See also https://cqdump.wordpress.com/2016/02/24/tarmk-and-san/
Kind regards,
Jörg
Views
Replies
Total Likes
Thanks for the additional article. I now have a clear picture of how the mmap mechanism works!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies