Is Storage Hierarchy Dead? Co-located Compute-Storage NVRAM-based Architectures for Data-Centric Wor

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Is Storage Hierarchy Dead? Co-located Compute-Storage NVRAM-based Architectures for Data-Centric Wor
# 1  
Old 11-09-2010
Is Storage Hierarchy Dead? Co-located Compute-Storage NVRAM-based Architectures for Data-Centric Wor

HPL-2010-119 Is Storage Hierarchy Dead? Co-located Compute-Storage NVRAM-based Architectures for Data-Centric Workloads - Roberts, David; Chang, Jichuan; Ranganathan, Parthasarathy; Mudge, Trevor N.
Keyword(s): No keywords available.
Abstract: The increasing gap between the speed of the processor and the time to access the data in the disk has historically been offset with deeper and larger memory hierarchies with multiple levels of SRAM, DRAM, and more recently, Flash layers for caching. However, recent trends that point to a potential s ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

moving data from FS from one storage to FS in another storage

Hello, I need to move 5TB of data from DS8100 to DS3400 storage.This 5TB of data is spread across 5 file system and mounted on one AIX server. Same file system structure is created on DS3400 storage and mounted on the same AIX server. Can anyone provide the best way of moving data from... (16 Replies)
Discussion started by: kmvinay
16 Replies
Login or Register to Ask a Question
MooseX::Storage::Engine::Trait::OnlyWhenBuilt(3pm)	User Contributed Perl Documentation	MooseX::Storage::Engine::Trait::OnlyWhenBuilt(3pm)

NAME
MooseX::Storage::Engine::Trait::OnlyWhenBuilt - An engine trait to bypass serialization SYNOPSIS
{ package Point; use Moose; use MooseX::Storage; with Storage( traits => [qw|OnlyWhenBuilt|] ); has 'x' => (is => 'rw', lazy_build => 1 ); has 'y' => (is => 'rw', lazy_build => 1 ); has 'z' => (is => 'rw', builder => '_build_z' ); sub _build_x { 3 } sub _build_y { expensive_computation() } sub _build_z { 3 } } my $p = Point->new( 'x' => 4 ); # the result of ->pack will contain: # { x => 4, z => 3 } $p->pack; DESCRIPTION
Sometimes you don't want a particular attribute to be part of the serialization if it has not been built yet. If you invoke "Storage()" as outlined in the "Synopsis", only attributes that have been built (ie, where the predicate returns 'true') will be serialized. This avoids any potentially expensive computations. This trait is applied to an instance of MooseX::Storage::Engine, for the user-visible version shown in the SYNOPSIS, see MooseX::Storage::Traits::OnlyWhenBuilt METHODS
Introspection meta BUGS
All complex software has bugs lurking in it, and this module is no exception. If you find a bug please either email me, or add the bug to cpan-RT. AUTHOR
Stevan Little <stevan.little@iinteractive.com> COPYRIGHT AND LICENSE
Copyright 2007-2008 by Infinity Interactive, Inc. <http://www.iinteractive.com> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2009-08-11 MooseX::Storage::Engine::Trait::OnlyWhenBuilt(3pm)