#ZVOL - Twitter Hashtag

over 1 year ago

Monthly Dividend Alert: $ZVOL Volatility Premium Plus ETF Distribution Rate: 45.00% Next ex-date: 6/26/25 30-Day SEC Yield: 1.77% Data as of 05/31/25. For standardized performance, visit https://t.co/Rn8VEHJMKB $ZVOL #ZVOL #VolatilityShares

VolShares's tweet photo. Monthly Dividend Alert: $ZVOL Volatility Premium Plus ETF
Distribution Rate: 45.00%
Next ex-date: 6/26/25
30-Day SEC Yield: 1.77%
Data as of 05/31/25.
For standardized performance, visit https://t.co/Rn8VEHJMKB $ZVOL #ZVOL #VolatilityShares https://t.co/XztdBm3L9t

2

5

1

0

1K

Volatility Shares

@VolShares

over 1 year ago

Monthly Dividend Alert: $ZVOL Volatility Premium Plus ETF Distribution Rate*: 36.92% Next ex-date: 4/28/25 30-Day SEC Yield*: 2.27% *Data as of 03/31/25. For standardized performance, visit https://t.co/Rn8VEHKkA9 $ZVOL #ZVOL #VolatilityShares

VolShares's tweet photo. Monthly Dividend Alert: $ZVOL Volatility Premium Plus ETF

Distribution Rate*: 36.92%
Next ex-date: 4/28/25
30-Day SEC Yield*: 2.27%

*Data as of 03/31/25. For standardized performance, visit https://t.co/Rn8VEHKkA9
$ZVOL #ZVOL #VolatilityShares https://t.co/qV5zmvKsi2

1

6

0

2K

Devoted Dividend Investor

@DevotedDividend

over 1 year ago

#ZVOL Volatility Premium Plus ETF ~ 30% yield

1

9

0

1

1K

john yoepp @JYoepp

about 2 years ago

@6_Figure_Invest #ZIVB changing its symbol to #ZVOL according to a supplement to the summary prospectus distributed on September 23

0

1

0

104

Felix Palmen 📯 @[email protected] @8bitsound

over 3 years ago

@extremecompute @freebsd_bot In my private scenario, my zpool lives on spinning disks, TRIM for them doesn't make any sense. Still, TRIM from a guest makes sense for sure as #bhyve can somehow shrink the #zvol in response 😉

1

2

0

46

Felix Palmen 📯 @[email protected] @8bitsound

over 3 years ago

@extremecompute @freebsd_bot I'm pretty sure reclaiming space by TRIM in the guest only works with a (sparse) #zvol as backing storage. To me, this is a valuable reason. But there really shouldn't be a performance penalty 😳 I wonder how this is even possible ....

1

2

0

29

Felix Palmen 📯 @[email protected] @8bitsound

over 3 years ago

I will keep the #zvols as they enable to minimize actually required disk space: A sparse #zvol actually shrinks when the #bhyve guest issues a TRIM (IIRC since #FreeBSD 12). But I might just try the #NVME emulation cause: can't hurt 😎

3

1

0

167

@[email protected] Ph.D 👨🏻‍💻🧬🌊🐕📷 @BenjaminHCCarr

over 6 years ago

Last week #FreeBSD #ZFS merged into #OpenZFS Up until this change, sync #ZVOL writes were done serially. But with the new code, ZVOLs are processed concurrently with sync writes in parallel. "The result is that the throughput of sync writes is tripled."” https://t.co/ZVBn4VqIA3

BenjaminHCCarr's tweet photo. Last week #FreeBSD #ZFS merged into #OpenZFS
Up until this change, sync #ZVOL writes were done serially. But with the new code, ZVOLs are processed concurrently with sync writes in parallel.
"The result is that the throughput of sync writes is tripled."” https://t.co/ZVBn4VqIA3 https://t.co/KlYe3iWtj6

0

17

9

0

♏αϲԋїҽl @mpronk89

over 7 years ago

The biggest 5 indexes are 33gb out of 77gb total, so this should definitely be optimized. We're also going to double RAM to 32gb, for obvious reasons. It's nice to see the two #zvol SSDs filling the RAM with 500mB/s whenever a new index has to be read from disk however :)

1

2

0