Hi,

We have a Storwize V5030F with 24 SSD disks. In order to have as much storage available as possible we made one large datastore with compression and dedupping enabled.

Now, it turns out we have plenty of storage available because of dedupping but also very poor performance. Therefore we consider changing compression/dedupping to thin provisioning/dedupping. In the GUI it looks like it's just a simply "click".

So to my questions:

1) Am I correct assuming that disabling compression will result in better performance? Or is it perhaps dedupping that is the cause of this alone? Our earlier performance tests shows that compression has an almost 50% performance penalty, but it's been a while since we made that test, and we have no experience with dedupping up until now.

2) If we change the capacity savings setting... What exactly will happen? According to the documentation a volume copy will be created in the background, but what exactly can we expect? Will it take a long time? Will there be a performance penalty while the operation is happening?

I hope someone has experience with this. Thanks.

/Rasmus