I¿ve got a request to create some 500GB meta volumes on our DMX-3
I¿ve read a recommendation to keep meta member quantity to a power of two. 2,4,8,16 etc¿. I have a need to create a few 500GB Meta. Based on the size of the logical volumes I have created I can use 32 members to create a 539.5 GB Meta and stick to the power of 2. Or I can create a 30 member volume to create a 505.8 GB disk.
My question is, what is the advantage to sticking to the power of 2, is it worth wasting the 2 extra disks (33GB) of disk space to stick to the 32 members?
The main reason for suggesting "power of 2" is that usually DA processors comes in power of 2 (at least it was always true in the past, not that true with DMX3/4) .. Using 2-4-8 members will hopefully spread the workload on all DA processors evenly. Even if this suggestion is still true, it usually applies to our CEs since when they define the binfile they can look easily at where the volumes are in the backend.
When you (our belove customer) create metavolumes, you usually have to "recycle" volumes previously used by other hosts .. so usually you tend to use what's available (in a true DIY style ) .. I love DIY .. however when it comes to performances it may give not-that-good results (I'd say "poor results" but I don't want to start another fight .. Allen everything OK with your switches?? )
Also note that the general rule (power of 2) works better when you have plenty of volumes and they are well-spread in the backend .. We had customers complaining for poor performances of 8-way metavolumes .. But the main reason for poor performances was that the volumes choosen to build the meta was on the same 4 drives.
So, in a word .. it depends
You can form metavolumes as big as you want however please be carefull in choosing volumes spread on differend drives in the backend unless you want poor performances
I think that Michael Lee may shade more light on this topic .. however since he is very busy you have to be happy with my answer
Good question Christian... and I'm hoping someone has a good answer. I've never heard this recommendation myself (I may have missed something in a best practices doc though). If there is a strong technical reason for this it may make a significant difference in how we allocate.
BTW Stefano - I wouldn't have argued with you on that one... you did say "may"
And the switches are fine. Apparently someone got reprimanded for telling me to do something that would break our fabric, and we've been promised "it won't happen again". Personally I was more worried about it happening to someone else who was more trusting and less informed *lol*
I don't make a penny off it. I bet if I let our Vendor Relations team loose on this I'd get something out of it though. It would probably just translate into bigger discounts on hardware though
Really though, this is a product that has made a huge impact at our site. ECC is so slow with DMX work that it is almost unusable. Command line is fast but more prone to error. SMC gives me the best of both worlds. GUI to help avoid the fat finger errors, and speed of execution. Plus little bonuses like putting good metas together for me and allowing me to copy flag setting from an existing FA port to another by selecting the one I want to copy.
The engineers who worked on this deserve a lot of credit... and I told them so at EMC World. If you think I'm excited about this product you should hear them talk about it
xe2sdc
6 Operator
•
2831 Posts
982
0
Posted August 13th, 2008 07:00
Even if this suggestion is still true, it usually applies to our CEs since when they define the binfile they can look easily at where the volumes are in the backend.
When you (our belove customer) create metavolumes, you usually have to "recycle" volumes previously used by other hosts .. so usually you tend to use what's available (in a true DIY style
I love DIY .. however when it comes to performances it may give not-that-good results (I'd say "poor results" but I don't want to start another fight .. Allen everything OK with your switches??
Also note that the general rule (power of 2) works better when you have plenty of volumes and they are well-spread in the backend .. We had customers complaining for poor performances of 8-way metavolumes .. But the main reason for poor performances was that the volumes choosen to build the meta was on the same 4 drives.
So, in a word .. it depends
You can form metavolumes as big as you want however please be carefull in choosing volumes spread on differend drives in the backend unless you want poor performances
I think that Michael Lee may shade more light on this topic .. however since he is very busy you have to be happy with my answer