Page 1 of 1

One global L1 cache pool - just an idea

Posted: Thu Dec 04, 2014 5:31 pm
by AndyKnight
Just thinking about what would could be changed in this product to make it more flexible and the things I keep coming back to are the L1 & L2 cache sizes and configurations.

How about one global L1 cache pool for all volumes so that resources can be expanded within a system without having to re-create all the virtual volume configs and the cache amount is not "fixed" to any one volume. The system would manage the cache assignment to each virtual volume so adding additional memory to a system would require no volume level changes, the system would just allocate more memory to existing volumes based on usage etc. You could have an manual override to allow specific settings to be made per volume.

I can see why doing this for L2 might be a real problem but the ability to change the L2 size once a volume has already been configured would be nice.

The other basic thing is to put a "back" button on the volume configuration wizard. It's really annoying without it!!

Thanks

Andy

Re: One global L1 cache pool - just an idea

Posted: Fri Dec 05, 2014 4:39 pm
by anton (staff)
1) We're working on a shared caches between all the volumes. However upcoming version will have shared deduplicated cache and dedicated non-shared ones (much small this time) so it may be we'll end with this design.

2) There's no differences between L1 and L2 as both have to be in sync.

3) There's "back" button on all the wizards. It's MSFT standard wizard design :)
AndyKnight wrote:Just thinking about what would could be changed in this product to make it more flexible and the things I keep coming back to are the L1 & L2 cache sizes and configurations.

How about one global L1 cache pool for all volumes so that resources can be expanded within a system without having to re-create all the virtual volume configs and the cache amount is not "fixed" to any one volume. The system would manage the cache assignment to each virtual volume so adding additional memory to a system would require no volume level changes, the system would just allocate more memory to existing volumes based on usage etc. You could have an manual override to allow specific settings to be made per volume.

I can see why doing this for L2 might be a real problem but the ability to change the L2 size once a volume has already been configured would be nice.

The other basic thing is to put a "back" button on the volume configuration wizard. It's really annoying without it!!

Thanks

Andy

Re: One global L1 cache pool - just an idea

Posted: Sat Dec 06, 2014 10:10 am
by AndyKnight
Anton, I do apologize. There was me looking for the back button in the pre 2012/windows 8 location (i.e. alongside the "next" button) where of course it is now in the top left hand corner.

Thanks for pointing that out!

Andy

Re: One global L1 cache pool - just an idea

Posted: Mon Dec 08, 2014 8:54 am
by anton (staff)
Honestly you're not the first (or second, or third...) to complain. Do you think it makes any sense to basically duplicate "Back" button in our wizards? To have some retro or old-school design?
AndyKnight wrote:Anton, I do apologize. There was me looking for the back button in the pre 2012/windows 8 location (i.e. alongside the "next" button) where of course it is now in the top left hand corner.

Thanks for pointing that out!

Andy

Re: One global L1 cache pool - just an idea

Posted: Tue Dec 09, 2014 8:04 pm
by AndyKnight
I would leave it. People will soon get used to the windows 8/2012 look and feel!

Re: One global L1 cache pool - just an idea

Posted: Wed Dec 10, 2014 2:59 am
by anton (staff)
OK :)
AndyKnight wrote:I would leave it. People will soon get used to the windows 8/2012 look and feel!