Mailing-List: contact user-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hama.apache.org
MIME-Version: 1.0
In-Reply-To: <40165489.10f79.140e65f052a.Coremail.wangzhigang1210@163.com>
References: <40165489.10f79.140e65f052a.Coremail.wangzhigang1210@163.com>
Date: Wed, 4 Sep 2013 10:59:42 +0900
Message-ID: 
 <CAGQgZQQmYTFrVPt2yKAqA=nd-PfEkSBDEOJN1bbMFN9PKyz4AA@mail.gmail.com>
Subject: Re: for graph processing, hama is disk-resident or memory-resident?
From: "Edward J. Yoon" <edwardyoon@apache.org>
To: "user@hama.apache.org" <user@hama.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

You cannot use the disk-based vertices storage and queue at the moment
but it will be supported in the future. We're under heavy development.


On Wed, Sep 4, 2013 at 9:28 AM, wangzhigang1210 <wangzhigang1210@163.com> w=
rote:
> Hi,
> Recently, I read source code of Hama on Graph API. And I have a question =
about the disk-resident and memory-resident issue.
> I find that there are two classes for maintaining vertices: ListVerticesI=
nfo.java and DiskVerticesInfo.java. The latter supports disk operations. Ho=
wever, in the class of GraphJobRunner.java, the class is set as ListVertice=
sInfo in the function setupFields. Thus, it seems that the version of disk =
is unusable for Graph API.
> Similarly, in the function of GraphJob.submit(), the version of message q=
ueue is also set as SortedMessageQueue instead of DiskQueue.
> So, for graph processing, I want to know whether Hama is a disk-resident =
system or not.
> Thanks,
> Zhigang Wang


--=20
Best Regards, Edward J. Yoon
@eddieyoon