Skip to Content
Last modified by Drunk Monkey on 2024-09-01 09:30
From version 3.1
edited by Drunk Monkey
on 2024-09-01 09:30
Change comment: There is no comment for this version
To version 2.1
edited by Drunk Monkey
on 2024-09-01 09:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -67,8 +67,7 @@
67 67   logs
68 68   mirror-1 ONLINE 0 0 0
69 69   ata-OCZ-REVODRIVE_OCZ-69ZO5475MT43KNTU-part1 ONLINE 0 0 0
70 - ata-OCZ-REVODRIVE_OCZ-9724MG8BII8G3255-part1 ONLINE 0 0 0
71 -{{/code}}
70 + ata-OCZ-REVODRIVE_OCZ-9724MG8BII8G3255-part1 ONLINE 0 0 0{{/code}}
72 72  
73 73  == SLOG Life Expectancy ==
74 74  
... ... @@ -101,8 +101,7 @@
101 101   mirror 1.46M 3.72G 20 0 285K 0
102 102   ata-OCZ-REVODRIVE_OCZ-69ZO5475MT43KNTU-part1 - - 20 0 285K 0
103 103   ata-OCZ-REVODRIVE_OCZ-9724MG8BII8G3255-part1 - - 20 0 285K 0
104 ------------------------------------------------- ----- ----- ----- ----- ----- -----
105 -{{/code}}
103 +------------------------------------------------ ----- ----- ----- ----- ----- -----{{/code}}
106 106  
107 107  == Conclusion ==
108 108  
... ... @@ -109,7 +109,6 @@
109 109  A fast SLOG can provide amazing benefits for applications that need lower latencies on synchronous transactions. This works well for database servers or other applications that are more time sensitive. However, there is increased cost for adding a SLOG to your pool. The battery-backed DRAM chips are very, very expensive. Usually on the order of $2,500 per 8 GB of DDR3 DIMMs, where a 40 GB MLC SSD can cost you only $100, and a 600 GB 15k SAS drive is $200. Again though, capacity really isn't an issue, while performance is. I would go for faster IOPS on the SSD, and a smaller capacity. Unless you want to partition it, and share the L2ARC on the same drive, which is a great idea, and something I'll cover in the next post.
110 110  
111 111  ----
112 -
113 113  (% style="text-align: center;" %)
114 114  Posted by Aaron Toponce on Thursday, December 6, 2012, at 6:00 am.
115 115  Filed under [[Debian>>url:https://web.archive.org/web/20210430212906/https://pthree.org/category/debian/]], [[Linux>>url:https://web.archive.org/web/20210430212906/https://pthree.org/category/linux/]], [[Ubuntu>>url:https://web.archive.org/web/20210430212906/https://pthree.org/category/ubuntu/]], [[ZFS>>url:https://web.archive.org/web/20210430212906/https://pthree.org/category/zfs/]].
... ... @@ -116,9 +116,8 @@
116 116  Follow any responses to this post with its [[comments RSS>>url:https://web.archive.org/web/20210430212906/https://pthree.org/2012/12/06/zfs-administration-part-iii-the-zfs-intent-log/feed/]] feed.
117 117  You can [[post a comment>>url:https://web.archive.org/web/20210430212906/https://pthree.org/2012/12/06/zfs-administration-part-iii-the-zfs-intent-log/#respond]] or [[trackback>>url:https://web.archive.org/web/20210430212906/https://pthree.org/2012/12/06/zfs-administration-part-iii-the-zfs-intent-log/trackback/]] from your blog.
118 118  For IM, Email or Microblogs, here is the [[Shortlink>>url:https://web.archive.org/web/20210430212906/https://pthree.org/?p=2592]].
119 -
120 120  ----
121 121  
122 122  {{box title="**Archived From:**"}}
123 -[[https:~~/~~/web.archive.org/web/20210430212906/https:~~/~~/pthree.org/2012/12/06/zfs-administration-part-iii-the-zfs-intent-log/>>https://web.archive.org/web/20210430212906/https://pthree.org/2012/12/06/zfs-administration-part-iii-the-zfs-intent-log/]]
119 +[[https:~~/~~/web.archive.org/web/20210430213532/https:~~/~~/pthree.org/2012/12/04/zfs-administration-part-i-vdevs/>>https://web.archive.org/web/20210430213532/https://pthree.org/2012/12/04/zfs-administration-part-i-vdevs/]]
124 124  {{/box}}