I was under the impression HAMMER was a parallel filesystem. sorry
On Wed, Aug 12, 2009 at 1:04 AM, Matthew
Dillon wrote:
>
> :
> :The I/O bottleneck is coming from the disk subsystem and network. I
> :was wondering if HAMMER can do parallel filesystem implementation
> :similar to GPFS or Lustre.
:
:The I/O bottleneck is coming from the disk subsystem and network. I
:was wondering if HAMMER can do parallel filesystem implementation
:similar to GPFS or Lustre.
:
:Also, the reads/writes are random access there is very little
:sequential streaming, but the files are large.Each file is around
The I/O bottleneck is coming from the disk subsystem and network. I
was wondering if HAMMER can do parallel filesystem implementation
similar to GPFS or Lustre.
Also, the reads/writes are random access there is very little
sequential streaming, but the files are large.Each file is around 30GB
each
:I am a student doing fluid dynamics research. We generate a lot of
:data (close to 2TB a day). We are having scalability problems with
:NFS. We have 2 Linux servers with 64GB of RAM, and they are serving
:the files.
:
:We are constantly running into I/O bottle neck problems. Would hammer
:fix the
I am a student doing fluid dynamics research. We generate a lot of
data (close to 2TB a day). We are having scalability problems with
NFS. We have 2 Linux servers with 64GB of RAM, and they are serving
the files.
We are constantly running into I/O bottle neck problems. Would hammer
fix the scalabi